[edit] also any interaction with storage / database isn't fun either, unless you use some ORM frameworks, and then you have some even bigger problems.

Then a lot of things about the way code should be structured can change. If you're not editing by hand, and want to limit the scope of changes, and have AI tools to make future edits faster... THEN you can have a lot of redundancy in your code. You can just not have complex code that shares responsibility and instead have redundant repeated code that solves one problem differently.

It's not what I would advocate for every single part of every program, but many things now make sense to be structured in this way. Separate out concerns way more, and not try to have complex solutions that solve many problems at once, and favour repetitive code slightly more.

Much as you would structure a project if you had some junior programmers, you might have sections that only seniors should be touching - complex cores and difficult parts where you have way more oversight. And use more AI in the areas where you'd let juniors do scut work.

Ask your AI to write tests and to review the code, of course /s

> And, what kind of solution needs 10,000 lines of code added to it daily?

In the first days, adding 10,000 useful lines a day can be very helpful. It means you get your MVP out earlier and/or makes it way easier to experiment with different ways to solve a problem.

A. you are doing this "full time"

B. Know what to build

C. More importantly you know "how" you want it built and you push the llm to refactoring regularly in your style.

I don't buy into the "let the agent code for 6 hours straight" agentic nonsense. I review every (big) change and just saving me stackoverflow/Google visits has been a huge productivity booster. Heck I wrote css, proto plugins, dsl parsers, simple games and more because now I needed much less "onboarding" times.

Better yet, feedback from these kind of tools is exactly what AI is great at in iteratively resolving so you don't have to review code below your standard of quality.

Or: too much weed tweeting.

Twitter is such a superficial format that obliterates all context, reason, and sense of humanity. I'm still 100% unsure what the intent of that conveyance was. Brain fart? That's why I don't tweet. Also, I'm too old.

Looking at the code, there is a good chance this codebase is vulnerable to SQL injection.

When people say "I did this" showing something they did with AI, the reality is "I asked an AI for this". Okay, not every time, but something on this scale would, they don't even know what those 10K lines of code do, they asked and received.