http://fluri.computerscience.ch Just for the sake of it... Sat, 10 Jul 2010 20:09:52 +0000 http://wordpress.org/?v=2.8.6 en hourly 1 http://fluri.computerscience.ch/2009/11/clean-code-developer-3/ http://fluri.computerscience.ch/2009/11/clean-code-developer-3/#comments Wed, 04 Nov 2009 19:30:24 +0000 bfluri http://fluri.computerscience.ch/?p=143 It’s time to replace the Clean Code Developer bracelet again. The next color, and grade respectively, is the yellow bracelet. Now, the principles become more interesting; The yellow bracelet principles are the foundation of clean object-oriented design. Although they are not that easy to fulfill every time, they should be followed as eagerly as possible. The principles and practices are:

1. Interface Segregation Principle: Clients should not be forced to depend upon interfaces that they do not use.
2. Dependency Inversion Principle: a) High level classes should not depend upon low level modules. Both should depend upon abstractions. b) Abstractions should not depend upon details. Details should depend upon abstractions.
3. Liskov Substitution Principle: a) subclasses have to fulfill the invariants of the superclass. Post-conditions of methods in the superclass have to be fulfilled by overriding methods in subclasses.
4. Principles of Least Astonishment: Avoid side-effects. Use, for instance, the command and query separation principle of Bertrand Meyer (Object-Oriented Software Construction).
5. Information Hiding Principle: Well, that’s not a principle, that’s an order
6. Complex Refactorings: See the Refactoring book by Martin Fowler, his Refactoring Web site, or the Refactoring to Patterns book by Joshua Kerievsky.
7. Automated Unit Tests
8. Mockups: For Java I recommend JMockit or mockito.
9. Code Coverage: I recommend Cobertura (free) or Clover (commercial) which both integrate nicely into Hudson.

]]> http://fluri.computerscience.ch/2009/11/clean-code-developer-3/feed/ 0