Have you ever seen or even developed a long, complex setup method in JUnit? Maybe it was because the production code was violating the Law of Demeter. Here's another Robert Martin Craftsman style entry.

This blog entry attempts to clear up the confusion among the terms property, field, instance variable, and attribute.

Ever have a constructor with 72 parameters? No, that wasn't a typo. How would you go about refactoring it? [...]

Here's an analogy to explain the precondition and postcondition covariance and contravariance rules of design by contract (DBC) in an inheritance/implementation hierarchy. These rules support the Liskov substitution principle (LSP) [...]

When used judiciously, the technique of adding collection-related utility methods on an object has its benefits.

A set of low level Eclipse refactorings commonly used together when refactoring unit tests.

This entry discusses a controversial, yet practical technique for refactoring test methods into a concise specification of test cases for a production class method.

The technique of coding by intention (along with test-driven development) is the first step in crafting elegant software.