The best AI coding habit I added was making mistakes cheap to undo
One thing I underestimated with AI coding:

The problem isn't always that the agent makes a bad change.
It's that a bad change can touch five things before you notice it.
I started treating larger AI tasks differently.
Instead of:
“Build this feature.”
I break it into changes where I can comfortably say:
“If this goes wrong, I can throw this away and lose 10 minutes.”
That means smaller commits, smaller scopes, and checking the app between meaningful changes.
It feels slower while the agent is working.
But debugging becomes much faster because I know roughly where the problem entered.
The biggest shift for me was realizing that AI speed isn't just how quickly it writes code.
It's also how cheaply you can recover when it writes the wrong code.
How are you keeping AI-generated changes easy to undo?
Replies