Articles, page 2

Spot classes that solve the same problem differently, extract the common part into a generic pattern, and replace old code step by step.

A tongue-in-cheek guide to making your app buggy: skip unit tests and more, plus answers to the usual excuses for not testing.

A breakpoint that only fired while I was making coffee, and how the browser's idle API turned out to be the culprit.

Go beyond TODO and FIXME: set up custom IDE labels like IMPROVE or QUESTION to keep your code notes organised.

Stop agonising over class names: start with a temporary name like Foo, implement the logic, then name it by what it actually does.