undefined | Better HN

0 pointsblub3y ago0 comments

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.

0 comments

2 comments · 2 top-level

oaiey3y ago

I 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.

larve3y ago

yes 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.

j / k navigate · click thread line to collapse