Yes. This is the result of the industry being led by only managers and non-technical people who scuff when engineers who talk about taking more time to do things properly as if they are just fulfilling their own personal creative needs. As a result the engineers who are just willing to make leadership happy are the ones who end up making technical decisions, usually short-sighted that leads to compounding complexity and lots of headaches down the line.

I've always thought that good engineering should go smoothly by definition. You shouldn't be juggling a ton of bugs and broken develompent pipelines. The problem is justifying this in a work culture that doesn't care about quality and is stuck looking at numbers that can be immediately justified.

There are plenty of decades old codebases written in old guard languages that were suffering the same fate pre-ai. What is old is new again.

We will just repeat the same pattern, have the latest and greatest frontier models rewrite the software just like how many desktop monoliths moved to React SPAs.

The real winners are frontier labs, we pay them to write black box software and we pay them to rewrite the software.

I think unfortunately companies are going to have to learn the extremely hard way what happens when your engineers no longer understand any of your code. The drive to eliminate institutional knowledge to create a perfectly replaceable worker was always dumb at best, and just leads to car crshes