A billing module everybody agrees should be separate, a team of four, and 88 classes that reference it. The boundary, drawn in code rather than in conversation.
A class named OrderFactory whose only method mapped one flat structure onto another flat structure with different field names. The name mattered more than it should have: three…
Some operations are safe to repeat by construction, and recognising them saves a table and a transaction. Setting a value is safe and adjusting one is not, which…
A case is a singleton, so a mutable property on it would be shared by every reference in the process, and the language forbids properties outright rather than…