SWE.for vibe coders

For people who ship with AI ✨

Software engineering
for vibe coders.

You can already build things. This is the stuff the AI never sat you down and explained — version control, testing, not leaking your API keys — taught in short, interactive lessons you actually do, not just read.

Start with Version Control →See the curriculum
🧠

Concepts that click

Plain-language explanations with real examples — no CS-degree jargon, no gatekeeping.

🎯

Check yourself

Quick interactive questions after each idea so you know it landed before moving on.

🛠️

Do it for real

Each module ends with a hands-on exercise in an actual repo — the tools you already use.

The curriculum

Seven modules, built to be taken in order. Start anywhere, but version control first pays off everywhere else.

  1. 01🌳

    Version Control

    4 lessons

    Save points for your code

    What git actually is, commits as save points, branches, reading a diff, and undoing mistakes safely — the single highest-leverage skill for anyone shipping code.

  2. 02🤖

    Working with AI Tools

    4 lessons

    Drive the AI, don’t get driven

    Small changes, reviewing generated code, writing prompts as specs, and knowing when to distrust the machine. How to stay in control of a codebase the AI is helping you write.

  3. 03🔎

    Reading Code You Didn’t Write

    Coming soon

    Follow the thread

    Tracing how a program flows, searching a codebase, and making sense of a file you’ve never seen before — without reading every line.

  4. 04✅

    Testing Basics

    Coming soon

    Prove it works

    What a test actually is, why it saves you hours of manual clicking, and writing your very first one. Confidence to change code without breaking it.

  5. 05🚦

    Don’t Break Production

    Coming soon

    Safety rails

    Environments, secrets and .env files, why you never commit API keys, and basic security hygiene. The mistakes that are embarrassing to make and easy to avoid.

  6. 06🐛

    Debugging

    Coming soon

    Find the actual problem

    Reading stack traces, moving beyond console.log, and narrowing a bug down systematically instead of changing things at random.

  7. 07🚀

    Shipping

    Coming soon

    Get it out the door

    Pull requests, code review, what "deploying" means, and how to roll back when something goes wrong. Going from "works on my machine" to live.