Continuous Design

Shore's piece on continuous design argues that the architecture of a system should emerge through refactoring rather than through upfront design, and that this is not a licence for carelessness but a different kind of discipline. The essay is rooted in XP practice but the argument generalises: any claim about what a system should look like five years from now is more brittle than a claim about the single next improvement that makes it better. For product direction the useful lesson is epistemic — big architectural decisions are usually worse than a sequence of small ones, even when the sequence feels less heroic. Shore's broader work on XP and the craft of software is worth exploring. A short, principled essay.