Test-driven development

Write the failing test first, then the code that makes it pass, then clean up. Kent Beck's 2002 book put a name on the loop, and the argument about how literally to take it has never stopped.