Refactorings

Fowler's catalogue, curated down to the entries big enough to carry a post. Patterns says what to build; this says how to get there from the code that is already running. Each post takes one refactoring: the mechanism, where the cost goes, the shape of problem it fits, when it is the wrong move and what to do instead, and the Go to write it, with the before and after and the mechanical steps in between drawn out, because a refactoring is a sequence of safe states and a picture of the endpoint hides the part that matters. Part of Under the Hood.