>I have seen a cultural change around non-engineering professions moving in on decision-making-territory that would have previously been an engineer's. The sam

>I have seen a cultural change around non-engineering professions moving in on decision-making-territory that would have previously been an engineer's. The same thing happened where I work (as a developer), but a funny thing is, since most of the upper people are a bit clueless about the domain (it's formalized in the code, they don't read code, and their turnover is high), when my team asks questions about specifications, they can be redirected back to us, from people that know we know the details. We also often don't waste time with questions and just have meetings with specification people to explain them what they should actually have asked us to do. That said, things don't always work out as nicely, and every few years we still have to brace ourselves to survive architectural tidal waves from astronaut architects who seduced credulous management, which we do by fighting to keep our module purely domain-oriented and independent from any particular stack (other than its language).