But you can iterate over the code until you like it. If you don't review the code, you risk slop. But reviewing takes time, and most people don't do that in the prototyping stage, because the code might still significantly change. But as your project matures you become more critical of the code and you review it more closely. And over time you also get more feeling of how to work with the AI to get the results you want.

Yeah shit

yeah

Or you give them all specific little tasks that you think out. And then review their work of course. So yeah you are still needing to do a lot of work.

Well we now have those millions of manhours and monkeys in the form of AI ;)

Or sit in the back of the train rather than the front

Middle.

It was the rear carriage which derailed

... but it seems most casualties in this accident are the passengers in the first carriages of the second train.

You never know.

Common sense? Once you are used to dark mode at night, light mode seems crazy.

But still the hypothesis of the article holds stance. If you want a new feature, you still have to think it through and explain the AI how to implement it, and validate the result.

You might be able to do more with less, but that is with every technological advancement.

Regarding your experience, it sounds like your codebase is such good quality that it acts as a very clear prompt to the AI for it to understand the system and improve it.

But I imagine your codebase didn't get into this state all by itself.

After 15 years you can just replace them

He's on a race because he knows his time is limited, eventually the Epstein files will be exposed. Time will tell.