I’ve encountered my fair share of kluge code as well, Scott. But just because we encounter or inherit spaghetti logic and associated code from one developer does not mean every engineer who writes their own architecture is going to be writing crap code.

We’ve all written things, where if more time were permitted, things would have been much better. I wouldn’t be so quick to blame an individual engineer for crappy code. I’ve worked with TEAMS that at the end of the day the team leads forced us into an architecture that was terrible! We had no escape and just had to deal with the noise and clusterfu—

My point would be: Why even write with React/Typescript/Whatever when it all compiles to vanilla JS anyway. Just write the vanilla JS or use a library like jQuery to free-up some bloat. If you need to compile, it doesn’t get added to the stack, is my rule of thumb these days.

If you don’t know how to write clean reusable code without using a code-bloating framework, you shouldn’t be leading a team. It’s not that I don’t want to learn a new technology, it’s really all about not wanting to learn BAD HABITS which these frameworks ultimately teach us by complicating and bloating the codebase.