>you're going to end up with a system you don't 100% understand very quickly

This has been my experience with all software projects. Even if I wrote all the code, my understanding of how everything works and fits together decays.

( See the Forgetting Curves https://en.wikipedia.org/wiki/Hermann_Ebbinghaus )

▲

gridspy an hour ago | parent | next [-]

While that may be true, you can be confident that it works in a way you personally understand. Because you understood it in the past.

Also, if you finish your work on a module with care - you return to a module you can trust with clear boundraries and known flaws. This is not true of AI output.

	▲	youre-wrong3 an hour ago \| parent [-]
		No. You can absolutely build things with AI small or large and understand it. If you don’t understand it. Then you’re not caring about the output to begin with and not guiding it to build the solution you want.

▲

simonw 5 hours ago | parent | prev [-]

Yeah, that's a fair point. I have plenty of older projects where I no longer understand how they work despite having written the code myself.

I guess the key thing is that you need to be able to demonstrate to yourself that you understand the code at least once, because that means you should be able to revise how it works in the future.

You also can't evaluate if a solution is fit for purpose if you don't understand it.