My anxiety for where this is all going is as follows. Using AI for all your coding is a wet dream for CEOs because the goal is to fire all their engineering staff except for a handful of maintainers. However, it reminds me of trying to explain to your stakeholders why you need time to work on tech debt before it becomes a problem. There is no metric now that says there is a problem that’s easily measured but engineers are grinding their teeth trying to work within a system that is slowly degrading and is showing signs.

“Who cares, ship it, also we need this new feature next week. What do you mean it will take longer this time? Ridiculous, why didn’t you say something before?”

Likewise, the brainrot and lost knowledge, as well as possible new tech debt that fewer engineers working in their codebase understand, will eventually cause issues down the line. The same pressures will ensue causing stakeholders to ignore all the signs of degradation.

> “Who cares, ship it, also we need this new feature next week. What do you mean it will take longer this time? Ridiculous, why didn’t you say something before?”

That's the reason I tried to have most of my communication (and complaints) in written and auditable form.