Version control as your safety net for AI-speed changes.
BookNook works. Add a book, see the list, reload, still there. Sam is quietly smug, so she gets ambitious: mark a book as finished. She briefs the agent properly and lets it loose on the files.
Ten minutes later, the list renders nothing. One detail matters: an hour ago, the agent had insisted on making something called a commit first. Before we define that word, answer one question.
Predict the response
The agent rewrote render() and now the list draws nothing. Sam doesn't know what else it touched, that's the frightening part. She types:
You've broken the render and I don't know what else you changed. Honestly, how bad is this?
What do you think the AI will do?
The word for that save point is a commit, and the tool that keeps them is git. A commit isn't 'save file', your editor does that constantly. It's a photo of every file at one moment, kept forever, with a name you choose.
Games solved this decades ago: save before the boss fight. The agent is the boss fight. Watch the hour replay on a timeline.
This lesson is part of the full course
The free lessons are just the opening chapter. Unlock the rest of Code with AI to keep going.
AcademyLv 1 · 0