FOR PEOPLE BUILDING WITH AI
The invisible journey of one code change.
What happens after your AI changes the code? Follow one change from your computer, through GitHub and Vercel, to a live website.
I’m an ops person building with AI. I made this because I wanted to understand the why and the how behind what I was approving.
10 steps · A fictional app called Picnic · One common GitHub + Vercel setup
▼ SCROLL TO ENTER
THE WHOLE LOOP
Know what you’re saying yes to.
Branch → worktree (optional) → edit → commit → push → pull request → checks → preview → merge → live.
Before approving your next AI-generated change, ask:
- What changed? Show me the diff and explain why.
- What did we verify? Show me the checks and the working preview.
- What happens when we ship? Confirm the environment, data changes, and recovery plan.
Built by an ops person, learning with AI. This journey is the explanation I wanted when I started.
Explore the source and share feedback on GitHub ↗