Skip to main contentdfsdf

Dmitry Serebrennikov's List: Currently Reading

  • Clean Code

    • The ideal number of arguments for a function is zero (niladic). Next comes one (monadic), followed closely by two (dyadic). Three arguments (triadic) should be avoided where possible. More than three (polyadic) requires very special justification—and then shouldn't be used anyway.
    • "You know you are working on clean code when each routine turns out to be pretty much what you expected." Half the battle to achieving that principle is choosing good names for small functions that do one thing.

    8 more annotations...

    • User Stories are written by the customers as things that the system needs to do for them.
      • "By the customers" is the key here. This will make sure these stories matter and hopefully will make them measurable.

    • Each story will get a 1, 2 or 3 week estimate in "ideal development  time". This ideal development time is how long it would take to implement the story in code if there were  no distractions, no other assignments, and you knew exactly what to do.
      • "and you knew exactly what to do" - this does mean that "anyone can do it" but removes the ramp-up time from the equation.

    3 more annotations...

    • As of release 1.5, it is legal and desirable to do this, because covariant return types were introduced in release 1.5 as part of generics. In other words, it is now legal for an overriding method's return type to be a subclass of the overridden method's return type. This allows the overriding method to provide more information about the returned object and eliminates the need for casting in the client.
1 - 8 of 8
20 items/page
List Comments (0)