OP’s approach is one in a thousand.

Imho most of professional coders trade their time for oblivion.

The problem is that you really don’t remember anything about the code. It is not your creation.

It’s like a monkey in front of a slot machine, just pulling the lever and waiting to see if it hits the jackpot.

At the end of the day, it remembers that it pulled the lever. And how many times it won :)

Agentic-based coding with /goal and multiple agents coding together is another level…

But the issue remain imho - if there is an error, who is going to repair it?

>The problem is that you really don’t remember anything about the code. It is not your creation.

The next problem is few care about that, at any level: coders, managers, execs. Just want their feature churn.

The even worse problem (or maybe, a positive) is that most of that code and the products powered by it aren't needed either.