Start The World's Best Introduction to TDD... free!

Simple Design, Refactoring Comments

The stronger your refactoring skill, the more easily you can use architecture advice as guidelines instead of as rules to enforce. This makes it significantly more likely that you’ll invest wisely in architecture, rather than over- or under-​engineer.

Read on →

Read on →

Read on →

Read on →

Refactoring, Simple Design, Evolutionary Design Comments

The most common definition of “refactoring” suffers from a common weakness that creates big problems for a very specific group of people. I’d like to help.

Read on →

Simple Design, Refactoring Comments

Refactoring means rework, which means that we didn’t “get the design right the first time”. This can indicate a problem. It can also indicate a natural process of convergence towards a suitable design. Calling it “a code smell” seems to overstate the matter.

Read on →

Evolutionary Design, Refactoring Comments

Programmers routinely give up on TDD when they try to do it in their toughest, meanest, most-valuable legacy code. I understand their impulse, but I think they’re setting themselves up for failure and ultimately missing out.

Read on →

Microtechniques, Evolutionary Design, Refactoring, Integrated Tests Are a Scam Comments

Programmers routinely ask me for advice on which kinds of tests they ought to write: unit vs. functional, fast vs. slow, big vs. small. They keep saying “integration test” when they mean “integrated test”. We have made this confusing, so I’d like to take one step towards clarifying it.

Read on →

Tutorials Comments

Debug with automated tests: it’s systematic, it leaves a record of what we’ve learned, and it’s boring in the best possible ways.

Read on →

Simple Design, Refactoring, Evolutionary Design, Tutorials, Removing Duplication Deftly Comments

An example of test-first programming, focusing on adding behavior incrementally and removing duplication.

Read on →

Simple Design, Dependency Inversion Principle (DIP), Evolutionary Design Comments

Are you worried that all these little classes and interfaces are going to destroy your system’s performance? Maybe. More often, however, the bottlenecks are caused by bigger classes and fewer interfaces causing duplication in the design.

Read on →

The Little Things, Tutorials Comments

A concise guide for going from nothing to a working nodejs environment on Linux environments.

Read on →