I don't see how you can design a complete architecture before you start building. The simplicity principle is at play here. At any given moment, the system has exactly enough architecture to implement the current set of stories. 1/5
The architecture evolves incrementally as the system grows. Any up-front architecture based on guesswork will be bloated & overcomplex. That unnecessary complexity adds expense—everything takes longer, and you need to maintain things you don't need. 2/5
You must know exactly what's required to avoid that, and you don't know that upfront. Also, let's say you spend a year designing before you start building. The thing you design will be obsolete before you've written a line of code. 3/5
The FAA had precisely this problem when it hired IBM to create a new air traffic control system. Every year, they designed a system but never built it because new requirements and tech had emerged during the past year, so they started over. 4/5
This went on for ten years (!) before they just ditched the entire project and did it right. Start simple. Design incrementally. #noxp 5/5
• • •
Missing some Tweet in this thread? You can try to
force a refresh
