2 ms·
What this article seems to be missing, as does most of the comments here, is the distinction between software engineers and architects. Everyone likes to rip on
by jedberg 8y ago
What this article seems to be missing, as does most of the comments here, is the distinction between software engineers and architects. Everyone likes to rip on the “architects that do no real work”, but this is exactly the problem and architect solves.
Their job is to understand the macro picture, the user’s use cases and the business use cases, and be technical enough to then digest that all into tickets of small chunks of work such that the software engineer can implement the right thing. It is the architect that holds the context and hopefully passes the right amount of that context through the ticket.
In the author’s metaphor, it would be the architect who would design the electric and water grid and decide which houses go where and who will build them and how. And then monitor the whole project and change things as issues come up.