This article misses the point of frameworks like Angular. Its never been about whether a framework is qualitatively better that vanilla or some other framework. The issue is when your codebase and your team reach a certain size you need the baseline, predictability and the guard rails that a framework provides. Otherwise you risk your project spiraling into chaos.
All projects spiral into chaos unless there's a person or more who try to reduce the growth of entropy, all the time, framework or not.
And these days, LLM agent will just re-use existing patterns if prompted correctly, regardless of who in the team is using it or whether or not there's a public well known framework in place or not. So consistency should not really be an issue anymore even in a team.
We need some kind of screening for these high-stress PTSD inducing roles ... a Voight-Kampff test. Or limit the number of years one can be in these roles.
I work for a large company, and I can say that context switching is also a problem here. I guess it comes down to the organization, or maybe the individual team. But yeah, there isn't a week that goes by where a development task isn't interrupted by something.
I think you're right. I also think that what tends to bore an experienced dev may be less likely to bore a junior dev, just because it's newer to them.
My son will turn 6 soon. I think he's ready for Scratch (or at least Scratch Jr) but I'm not sure he's ready for BASIC. I guess I could him a printout of some code and see if he can type it in without errors...