Because all these idiots who pitched microservices super hard need to undo the mess they've created while self promoting themselves into new thought leadership roles.
They formed a partnership with some dev shop that's going to rebuild everything that I made (that's working great and scales well).
I asked her why, and she said "because they say that doing microsevices on Azure is better architecture".
There goes that bit of equity, I guess.
/shrug
However, I've definitely seen this problem even with legitimately strong, seasoned technical leadership, where the vision is great, but the team just doesn't have the skills to pull it off. You can't have good macro-engineering without good micro-engineering. The problem with the cambrian explosion of tech is that it obfuscates the basics that engineers need to understand. Junior engineers end up struggling just to stay on top of incidental complexity and many come to the conlusion that building good software is just about learning enough languages and tooling, when in reality they are barely keeping their head above water and never learn the deeper lessons of what works and doesn't in software systems.
Can you reasonably expect a junior engineer to push back here and generally get traction? If this architectural decision has been made, it’s been made. At higher levels.
>If everyone had better system design knowledge
I don’t think this is a junior devs fault - they’re junior, after all.
> but then it doesn’t work because the organization…
Bingo.
Spot on.
And how do you know you’re not a thought leader? You call yourself one