|
|
|
|
|
|
by andreskytt
1420 days ago
|
|
|
Plus, they miss a key point of architecture: sustainability. You might take the 30’ somewhere and draw a high-level model like the ones depicted in the article, but who has time to continuously validate that devs actually follow the blueprint and make decisions should a need to change emerge? Nobody. And that’s OK. Architecture is not a magical ding an sich to be pursued but a way to organize things to achieve specific strategic goals. And for a startup, that goal is to survive until the liftoff. This survival very seldom involves investing heavily into architecture. Some experienced devs are going to be fine, neither the business nor the organization nor the system is going to be complex enough to merit dedicated attention to architecture. And if they are, something is wrong elsewhere (typically leadership) |
|
|
To be fair, while I never expected Kant to get involved in startup thinking, architecture as (not) a goal in itself is a very good point.