The One-Way Doors That Remain
Almost every practice we have for building software was designed around an assumption that’s quietly stopped being true. Test coverage budgets, code review queues, refactoring debt, junior hiring pipelines, the ratio of product managers to engineers, the number of services we maintain, the cost of saying no to a feature. Each of these is a knob set somewhere on the dial, and the position of the dial was determined by a single underlying parameter: writing code was slow and expensive.