Welp. if the system prompt says to do one thing, and you're going to do some other thing; that will never end well.

More in general, I don't think there's good books on this yet. But if you want to try coding with AI, start out slow and scrutinize every edit first, get a feel for what kinds of mistakes are made and how they can be recovered from.

AI doesn't quite work like a human does. It's also not a magic wand; sorry! It's great that you can sort of have an 'compile english' now, but programming is still a skill.

I was full on AI camp. I built a lot of useless stuff.

I know deleted most of it and refactored it into an agile codebase with 40k lines less. My life is peace again.

I now use ai for scratch tests and the next edit function from jet brains.

For me it mostly is the same experience. Of course it is possible to steer AI a bit by writing rules for it to follow. But in the end, I'd never go live with a purely vibecoded app as of now, not only because it will be a maintenance hell but also due to its security issues which still occur a lot too.

Same for me. I spent 3 days dealing with AI crap, following it's thinking "process".

However it is great for "go add this username to this allowlist in this file"