Part 6
Verification And Safety
The discipline that separates people who ship working software from people who confidently ship broken software. Reading code you didn't write, git as a seatbelt, the verification habit, secrets management, data privacy, and what production deployment actually looks like for a small business. The most underrated Part in the curriculum, and the one most readers skip first.
Start with section 6.1 →- 6.1
Reading Code You Didn't Write
The single most important skill for vibe coders. Five things to spot in agent output, and the four-step workflow for not shipping the bug you didn't notice.
- 6.2
Git Discipline For Ai-generated Code
Git is your seatbelt. Commit before every agent run, branch per feature, read every diff, write commit messages the next session can understand.
- 6.3
Testing Without Being A Tester
The verification habit, made operational. Three to five happy paths, three to five edge cases, one to two failure modes. Eight tests, manually run, catch 90% of the bugs.
- 6.4
Secrets, Api Keys, And What Not To Put In A Prompt
The rules: never paste real secrets into a frontier model chat, never commit .env, never hardcode keys. A leaked secret is AFD by default.
- 6.5
Data Privacy: When Local Models Are Non-negotiable
Some data should never leave your machine. PHI, PII at scale, financial data, trade secrets, NDAs. The decision tree, and why most regulated data is also AFD.
- 6.6
The Deployment Cliff: Making It Run While You Sleep
Building an agent on your laptop is one thing. Having it work at 3 AM when you're asleep is a different thing. The Mac mini setup for production.