"My methodology works until junior devs show up and don't know how to code"
"My methodology just works... except all the times it doesn't and when it doesn't, it's your fault because you did it."
That's what I got from this article.
It's development itself that's the problem. Software is really complex and things take a long time to build. The relationship between the time it takes for management to say "build it" and to actually build it is asymmetrical. It requires many people to build things of significance. Coordinating understanding of things between people is a hard problem. Gaining the experience to know why you should or shouldn't do something takes years. During that time you have to be working on things and contributing to code bases.