2 ms·
So far I have not come across an architect role that made any sense. You just can't effectively design a dynamic technical system from a high horse looking dow
by ilaksh 11y ago
So far I have not come across an architect role that made any sense. You just can't effectively design a dynamic technical system from a high horse looking down without being involved in the implementation.
The reasons for this: you need tight feedback loops in engineering. If you accomplish that then you are iterating and constantly refining requirements, design, tests, implementation, even platform selection for various parts of the system. All of the feedback loops need to be observed and responded to in detail. Someone who is not doing coding is just not going to be able to contribute positively. They will not be able to see what is going on in terms of requirements changes, implementation challenges, technology changes, etc.
So a company with anything like a traditional software architect role is suspect of not understanding software engineering.