Yes, an entire client/server codebase written prior to AI existing has been made far better. More features that players report work (and I play it myself). Far more performance in a measurable way that is obvious to me and players. It can support larger maps, while running well in excess of 120fps when prior it couldn't get past 20fps. This was multiple performance issues that needed resolving. Not once did I look at the solutions that improved performance. I had Claude do byte and object level comparisons between versions to catch regression. I then played it myself to much joy.
When I release features, players report minor bugs, which I can fix in minutes by simply dumping their complaint into claude.
I worked on this codebase prior to LLMs and made slow progress, with many bugs. I did not know how to approach the performance problems, nor was I able to refactor the project to effectively have test and production environments reproducible. Claude did just fine.
It is 350k LoC, with over 138k as an Elixir app, 60k in tests/scripts, 65k Vue components, 45k JS, and more.
Coding is solved. Many people can't manage software engineering effectively. I don't know how much larger or how much more comparison is needed before this is accepted. Maybe it is "circular" reasoning like the dead comment says.
But it literally just works for me.
It works for me too. And I am keeping things very simple. Tell it what to do next. Check result. Rinse and repeat until I'm happy with the outcome. I do check the code diffs in produces, but only to get a rudimentary idea what it did. The results speak for themselves.