Fill blog course-link placeholders with the course URL (#76)

Co-authored-by: claude <claude@jpaul.io>
Co-committed-by: claude <claude@jpaul.io>
This commit was merged in pull request #76.
This commit is contained in:
2026-06-22 19:15:32 -04:00
committed by Claude (agent)
parent e5960c17ab
commit 3671541d6b
18 changed files with 41 additions and 37 deletions
+2 -2
View File
@@ -16,7 +16,7 @@ You've got an idea — *rewrite the storage layer*, *try a completely different
That hesitation is the tax you pay for not having a sandbox. This post is about removing it.
If you're new here: this is part of [The Workflow]([COURSE LINK]), a free course about all the engineering scaffolding *around* AI-generated code — the version control, the editor integration, the review reflex — that the model itself doesn't give you. A couple of posts back we [installed the safety net]([COURSE LINK]): Git, framed as undo for the AI. That safety net was perfect for *one* bad edit — commit, then `git restore` if the AI makes a mess. Today we go one size up: isolating a *whole line of experimental work* so you can keep it or throw it away as a single unit. That's a branch.
If you're new here: this is part of [The Workflow](https://git.jpaul.io/justin/ai-workflow-course), a free course about all the engineering scaffolding *around* AI-generated code — the version control, the editor integration, the review reflex — that the model itself doesn't give you. A couple of posts back we [installed the safety net](https://git.jpaul.io/justin/ai-workflow-course): Git, framed as undo for the AI. That safety net was perfect for *one* bad edit — commit, then `git restore` if the AI makes a mess. Today we go one size up: isolating a *whole line of experimental work* so you can keep it or throw it away as a single unit. That's a branch.
## What a branch actually is (it's less than you think)
@@ -64,7 +64,7 @@ One more thing that feels like magic the first time: when you `git switch` to an
Enough theory. The course runs on a tiny example app called `tasks-app` — a little command-line to-do tracker — and this is where branches stop being abstract. Make sure you're on a clean `main` first (`git status` should say "nothing to commit"), then spin up an experiment:
```bash
cd ~/workflow-course/tasks-app
cd ~/ai-workflow-course/tasks-app
git switch main
git status # must be clean
git switch -c experiment/priorities