11 ms·
If the architect from your second paragraph works closely with the dev team for prototyping and iterates on their feedback I don’t see anything wrong with that
by blub 4y ago
If the architect from your second paragraph works closely with the dev team for prototyping and iterates on their feedback I don’t see anything wrong with that approach.
- larve 4y agoyes exactly. I was referring to what I think the OP was rejecting, a rigid top down approach to software engineering, with the architect and their UML at the top, and the grunts and their editor at the bottom.
- oaiey 4y agoI agree. The architecture profession is radically different today than 20 years ago. However, there is a scale where that does not work anymore. Once you plan at the scale of 20 or more teams, "working closely" is very relative.