> Citation needed.

Citation is me and my own personal experiences with vibe coded software. If you have examples of stable, efficient, polished software created by AI, I'll gladly try them out.

Regardless, your comment is a perfect exhibit of the problem. You are seeing 100 AI generated PRs merged in a day and interpreting that as 100 improvements to the user experience, which probably sounds great when you tell it to your manager before asking for a promotion, but doesn't actually translate to reality and never has. Before AI, it was generally agreed upon that measuring quality of work by lines of code written, PRs merged, etc. made no sense, yet that wisdom seems to have been completely forgotten in favor of just watching the line go up.

How do you even know the improvements are "enormous" if you don't understand the code? Do you just occasionally glance at your terminal to see Claude going on about how it just found the smoking gun and made a critical fix to a load-bearing seam and go "whoa, that sounds important"? If those improvements and bug fixes really were so important, why were they not considered worth the effort to make before AI came along, or was your team simply incapable of making them before?

If you're the most senior developer working on the same codebase for 12 years, yet proudly state that an LLM understands it better than you do, I can't help but interpret that as an admission of incompetence, so letting AI do your work for you may really be an improvement, but it shouldn't be.