Play as Webslides

Dmitry Serebrennikov's List: Currently Reading

Clean Code
ProQuest Information and Learning - 9780136083238 - Clean Code: A Handbook of Agile Software Craftsmanship

proquest.safaribooksonline.com/...pref01 - Preview

on 2009-04-04
ProQuest Information and Learning - 9780136083238 - Clean Code: A Handbook of Agile Software Craftsmanship

proquest.safaribooksonline.com/...ch03lev1sec1 - Preview

on 2009-04-04
- 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...
- - Don't be afraid to make a name long. A long descriptive name is better than a short enigmatic name. A long descriptive name is better than a long descriptive comment.
  - The LOGO language used the keyword "TO" in the same way that Ruby and Python use "def." So every function began with the word "TO." This had an interesting effect on the way functions were designed.
  - There are two very common reasons to pass a single argument into a function. You may be asking a question about that argument, as in boolean fileExists("MyFile"). Or you may be operating on that argument, transforming it into something else and returning it. For example, InputStream fileOpen("MyFile") transforms a file name String into an InputStream return value.
  - My general rule for switch statements is that they can be tolerated if they appear only once, are used to create polymorphic objects, and are hidden behind an inheritance relationship so that the rest of the system can't see them
  - If a function does only those steps that are one level below the stated name of the function, then the function is doing one thing.
  - A somewhat less common, but still very useful form for a single argument function, is an event. In this form there is an input argument but no output argument. The overall program is meant to interpret the function call as an event and use the argument to alter the state of the system
  - So, another way to know that a function is doing more than "one thing" is if you can extract another function from it with a name that is not merely a restatement of its implementation [G34].
  - Try to avoid any monadic functions that don't follow these forms, for example, void includeSetupPageInto(StringBuffer pageText). Using an output argument instead of a return value for a transformation is confusing.
ProQuest Information and Learning - 9780131495050 - xUnit Test Patterns: Refactoring Test Code

proquest.safaribooksonline.com/9780131495050 - Preview

library on 2009-04-06
ProQuest Information and Learning - 9780136083238 - Clean Code: A Handbook of Agile Software Craftsmanship

proquest.safaribooksonline.com/...ch05lev1sec3 - Preview

on 2009-04-08
Academic Productivity » Diigo - Web Highlighter and Sticky Notes, a delicious killer?

www.academicproductivity.com/...ticky-notes-a-delicious-killer - Preview

on 2009-04-09 and saved by 16 people
User Stories

www.extremeprogramming.org/...userstories.html - Preview

xp on 2009-04-18 and saved by 6 people
- User Stories are written by the customers as things that the system needs to do for them.
- 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.
- 3 more annotations...
- - Less than 1 week and you are at too detailed a level
  - User stories should only provide enough detail to make a reasonably low risk
    estimate of how long the story will take to implement. When the time comes to implement the story developers will
    go to the customer and receive a detailed description of the requirements face to face.
  - You should try to keep stories focused on user needs and benefits as opposed
    to specifying GUI layouts.
The Spring Framework - Reference Documentation

static.springframework.org/...index.html - Preview

spring reference java on 2009-04-20 and saved by 21 people
ProQuest Information and Learning - 9780137150021 - Effective Java™, Second Edition

proquest.safaribooksonline.com/...pref01 - Preview

library on 2009-06-29
- 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 - 9 of 9

Showing 20▼ items per page

List Comments (0)

List Info

Dmitry Serebrennikov

9 items | 9 visits

Updated on 2009-06-29
Created on 2009-04-04

Category: Others

bookshelf

URL:

Dmitry Serebrennikov's List: Currently Reading

ProQuest Information and Learning - 9780136083238 - Clean Code: A Handbook of Agile Software Craftsmanship

ProQuest Information and Learning - 9780136083238 - Clean Code: A Handbook of Agile Software Craftsmanship

ProQuest Information and Learning - 9780131495050 - xUnit Test Patterns: Refactoring Test Code

ProQuest Information and Learning - 9780136083238 - Clean Code: A Handbook of Agile Software Craftsmanship

Academic Productivity » Diigo - Web Highlighter and Sticky Notes, a delicious killer?

User Stories

The Spring Framework - Reference Documentation

ProQuest Information and Learning - 9780137150021 - Effective Java™, Second Edition

List Info

Sponsored Links

Dmitry Serebrennikov's Public Lists (14)