> Shouldn't a senior engineer being trusted with this rather than a non-coder? There's your problem right there. If your Architects are non-coders then honestl

> Shouldn't a senior engineer being trusted with this rather than a non-coder? There's your problem right there. If your Architects are non-coders then honestly, they shouldn't be dictating the low level implementation detail, this should be left up to the engineering teams to work out. In the UK at least, Architect is a title you give a seasoned technical person who wanted a promotion pathway but without direct line management responsibility. It wasn't until relatively recently enterprise businesses recognised they needed to introduce career pathways for proven technical people who wanted to remain technical and not managerial/political. When I started (2003) the only way to get promoted was to start managing people and to let go of the technical work. Dread to think how many great engineers were lost to this old school thinking.