Re:Ask HN: Is there a better way to document complex softwar...
by pmontra on Sunday November 25, 2018 @12:07PM
(#18527673)
If the project is very large architects don't have time to code. Sometimes they can test something before taking decisions but all the production code is written by somebody else. Their role is more about meeting people and help the organization making the correct decisions.
[ Parent
| on HN ]
Re:Ask HN: Is there a better way to document complex softwar...
by maxxxxx on Sunday November 25, 2018 @01:37PM
(#18528112)
I am always wary of architects that don't code or at least aren't involved in the whole life time of the project so they have to feel the consequences of their designs. Our IT department is full of "architects" whose designs then get outsourced to India. Either their designs are crap that doesn't survive the first contact with reality or they are so trivial that pretty much anybody could do them. They spend a lot of time in meetings with important people though.
I find it much better to empower the senior devs of different teams to duke it out among them. Maybe the process is not as clean as having some genius architect divine the perfect architecture but it reflects reality much better.
Re:Ask HN: Is there a better way to document complex softwar...
by AlphaWeaver on Sunday November 25, 2018 @12:28PM
(#18527775)
I think this depends... I work at a Fortune 100 company, and I know architects that still code, despite being involved with large projects...
Re:Ask HN: Is there a better way to document complex softwar...
by fsloth on Sunday November 25, 2018 @12:23PM
(#18527754)
What is "very large"?
Re:Ask HN: Is there a better way to document complex softwar...
by pmontra on Sunday November 25, 2018 @01:29PM
(#18528074)
In my experience, a multi country mobile operator bootstrapping when 3G was a new thing 15+ years ago.