Shout out to my homies in RVA. There are so many complications to this issue. I imagine a long time ago things were less complex and more manageable. As you

Shout out to my homies in RVA. There are so many complications to this issue. I imagine a long time ago things were less complex and more manageable. As you build layer upon layer of new tooling on top of the past I feel things were just naturally going to get complex and unmanageable. It's almost like for us to have avoided this we would need some programming paradigm that stands the test of time and is flexible enough to meet today's needs. Which is probably impossible. Unless we are in the Cambrian explosion of tooling and frameworks and at some point we will achieve a steady state. That would be really cool to see in my lifetime. Every time I think "ah yes, this should be good enough" I am blindsided by the new shiny. That's also a separate topic. There's plenty of incentive to use the new shiny if it's not the right tool for the job. Tech gets hyped by the usual engines, CTO's buy into it, and then that's our tech stack. You need to have these new frameworks on your resume to become employable so when you start a new project you end up using one of them. I don't know what the solution to this is other than the hope that there's some general building blocks or concepts of software development that will be easy to make work with other building blocks.