1. 8
  1.  

  2. 7

    This is especially true if you subscribe to the ridiculous Church of 80-character Lines.

    I’m a member of that church, and I still use long method names where appropriate. I don’t see why the two are mutually exclusive.

    1. 3

      Not sure if I agree with bringing the verbosity of Objective-c to Ruby.

      It’s similar to writing, where it’s easy to write a long rambling paragraph but takes skill to write succinct short sentences that get the point across just as effectively.

      1. 2

        I’m definitely in the camp of being a bit more verbose in my Ruby than others, but that first method just seems crazy. I feel like just saying “make_person_an_outside_subscriber” would be sufficient, but I don’t have enough context to be certain.

        1. 1

          In theory, it’s always been there. Comes from smalltalk. Ruby is perl + smalltalk, much in the way objective-c is c + smalltalk, except ruby doesn’t force the named params style.

        2. 1

          This is especially true if you subscribe to the ridiculous Church of 80-character Lines.

          If I am getting anywhere close to 80 chars in ruby, generally I am being ridicules, and almost always leads to an extract variable.

          It’s not a hard and fast rule for me, often string literals will cause a line to wrap. but it is a great guideline (at least if you are not using a super verbose language), and leads to readable code.