2 ms·
This is the art in being a good architect. Let the chaos reign for a while and then tighten control when necessary. Start with a skeleton and let the teams fles
by oaiey 8y ago
This is the art in being a good architect. Let the chaos reign for a while and then tighten control when necessary. Start with a skeleton and let the teams flesh it out and sometimes break a bone. But once you can benefit from architecture start to enforce your architecture.
PS: European. German to be exact. We love to plan and over engineer.
- jungturk 8y agoAgreed - this results from the Last Responsible Moment principle: https://blog.codinghorror.com/the-last-responsible-moment/ https://blog.codinghorror.com/the-last-responsible-moment/ An effective architect assesses _when_ they should constrain choices to achieve the -ilities. For instance, in projects aimed at learning about the customer or market, you might reasonably defer many traditional architectural goals (maintainability, modifiability, perhaps even secury), while in projects aimed at creating durable long-term value in a well-understood space you probably wouldn't.