justin/ai-workflow-course
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(blog): fill course-link placeholders + align learner-dir path

Browse Source 
- Replace all 24 [COURSE LINK] placeholders across the 17 posts with the course URL
  https://git.jpaul.io/justin/ai-workflow-course.
- Align the learner working-dir path in the posts to ~/ai-workflow-course (matches
  the modules after the repo rename).
- blog/README: mark the course-link checklist item done; flag publish-time
  refinements (GitHub-mirror swap; repoint inline cross-post links to real
  jpaul.me post URLs).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
This commit is contained in:
Claude (agent)
2026-06-22 19:15:20 -04:00
parent e5960c17ab
commit 250189a60e
18 changed files with 41 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files
blog/07-branches-sandboxes.md
+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