I've seen such a thing, taken to an extreme where lazy, underskilled developers were running the show; overcomplicating, underdelivering, yet showered with praise -- and it's horrible to witness. A word of warning for anyone entering such a world: you will not change this environment and any attempts to do so will trigger an immune system response. The developers and clueless managers will circle the wagons in defense of the existing culture.
Lesson learned: don't interfere with "resume-driven development" organizations.
I suggest the following interview question: "Tell me about the technical capability of your management chain."
What about managers who have had experience like a decade ago and don't do much tech experience anymore.
I am stuck in such management chain at work where some guy up top thinks he is technical enough to dictate solutions based on couple conference youtube videos that he watches.
Half knowledge and false sense of technical prowess is more dangerous imo.
A manager should have the big picture and communicate it to the team. Then you could avoid a team member wasting time on something that’s not in the greater objectives or roadmap.
Do you think any of the "bullshit engineers engage in with respect to fad chasing, bikeshedding and other negative practices." will change in 20 years?
Its been almost 20 years since first coined and we _still_ have bike shedding problems