the death of the architect by Zach Tellman.
In his [Kent Beck] Extreme Programming (XP) methodology, design and implementation were interleaved. “There will never be a time,” he said, “when the system ‘is designed.’ It will always be subject to change, although there will be parts of the system that remain quiet for a while.”
A year later, Beck’s ideas were distilled into the Agile Manifesto. His notion of lightweight design became a preference for “responding to change over following a plan.” What’s the point of a plan that solves yesterday’s problems?
And then, three years after the Manifesto, Beck released the second edition of Extreme Programming Explained. It had been rewritten from scratch. There was not a single mention of metaphors or system architecture. Nor, really, any discussion of the future. In this iteration of XP, you simply moved from moment to moment.