A few weeks ago, I made a post about a very interesting video made by Miško Hevery intituled “The Clean Code Talks – Don’t Look For Things!”.

Today, I discovered that there is a PDF summarizing the important principles, with actually some very detailled examples also.

I really highly suggest to any programmer interested by unit testing to take the time to read this document.

It can be found on Miško Hevery’s website or you can directly download the pdf from this shortcut.

Here is a summary of the content of that pdf (this is taken directly from Miško Hevery’s website).

Flaw #1: Constructor does Real Work

Warning Signs

• new keyword in a constructor or at field declaration
• Static method calls in a constructor or at field declaration
• Anything more than field assignment in constructors
• Object not fully initialized after the constructor finishes (watch out for initialize methods)
• Control flow (conditional or looping logic) in a constructor
• Code does complex object graph construction inside a constructor rather than using a factory or builder
• Adding or using an initialization block

Flaw #2: Digging into Collaborators

Warning Signs

• Objects are passed in but never used directly (only used to get access to other objects)
• Law of Demeter violation: method call chain walks an object graph with more than one dot (.)
• Suspicious names: context, environment, principal, container, or manager

Flaw #3: Brittle Global State & Singletons

Warning Signs

• Adding or using singletons
• Adding or using static fields or static methods
• Adding or using static initialization blocks
• Adding or using registries
• Adding or using service locators

Flaw #4: Class Does Too Much

Warning Signs

• Summing up what the class does includes the word “and”
• Class would be challenging for new team members to read and quickly “get it”
• Class has fields that are only used in some methods
• Class has static methods that only operate on parameters

Be Sociable, Share!

• 
•