13 Matching Annotations
  1. Last 7 days
  2. Apr 2021
    1. “Who cares? Let’s just go with the style-guide” — to which my response is that caring about the details is in the heart of much of our doings. Yes, this is not a major issue; def self.method is not even a code smell. Actually, that whole debate is on the verge of being incidental. Yet the learning process and the gained knowledge involved in understanding each choice is alone worth the discussion. Furthermore, I believe that the class << self notation echoes a better, more stable understanding of Ruby and Object Orientation in Ruby. Lastly, remember that style-guides may change or be altered (carefully, though!).
    2. Similarly to fashion, code style reflects our credo as developers, our values and philosophy.
    3. Yet, it certainly is important to make the proper choices when picking up style. Similarly to fashion, code style reflects our credo as developers, our values and philosophy. In order to make an informed decision, it’s mandatory to understand the issue at stake well. We all have defined class methods many times, but do we really know how do they work?
    1. The best procedure is the one you don’t need. If the UI is crystal clear and leads the customer through a task, a procedure isn’t necessary. Start there.
    1. I actually think this is Not Constructive, since there's no absolute rule about which pairings can be joined into a single word or hyhenated, and it's pointless having "votes" here about each specific case. Follow a style guide if you have one, or search Google Books and copy whatever the majority do. Or just make your own decision.
  3. Dec 2020
    1. Include articles, such as the. Articles help readers and translation software identify the nouns and modifiers in a sentence. Examples Empty the container. The empty container
  4. Oct 2020
  5. Aug 2019
  6. Jan 2017