A lot of the post has more to do with js itself. The author talks about performance, but never addresses the fact that most juniors probably started in Python o

A lot of the post has more to do with js itself. The author talks about performance, but never addresses the fact that most juniors probably started in Python or Ruby. They didn't have to care about doing things the most efficient way, and could probably just use a framework to do what they wanted to do without caring about implementation. This lack of concern is not rectified by any of the senior engineers, and only appears once they are required to do something outside of a framework that provides decent performance. I don't want to come across as rude, but it seems strange that hiring a junior developer and introducing them to web development doesn't come with a guide on what to do or how to approach js. I don't quite understand how researching deep enough into Angular to find out about performance tweaks doesn't lead one to make a guide or tips for new hires. Sure, you can hope that they know what they are doing, but if you care enough to stop using a framework due to their bad habits it might be time to reflect and realize that the power given by a framework comes with more abilities and more pitfalls. This trade off is clearly demonstrated when the author talks about the "pit[s]" that junior engineers fall into. They look at code and see it works for one use and just use it in the other case because they have seen it work. It isn't all their fault that they are "very good at copy and pasting" because nobody has told them the steps to guide their code structure. I appreciate the author for sharing his views but it seems like it would be helpful to provide the list of pitfalls and ways to avoid them to his juniors instead of disliking frameworks.