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
+1 -1
View File
@@ -14,7 +14,7 @@ I'll admit this is the unit I was most excited to write, because it's the part I
So if the earlier units felt like careful infrastructure homework — version control, branches, review, CI — this is where it starts to feel like the future you were promised. Up to now everything we did kept the AI inside one box: **files in your repo.** It could read them, edit them, commit them. That's a lot. But the moment your question pointed one inch outside that box, the AI went blind.
This is the arc of **Unit 4 of [The Workflow]([COURSE LINK])** — four modules that take the AI from "edits my files" to "operates in my world." MCP gives it hands. Skills teach those hands a playbook. Then we secure the whole thing, because the day you give an AI hands is the day a stranger's code can use them. And finally we point all of it at the hardest, most common target there is: a giant codebase you didn't write. If you're new here, the [first post]([COURSE LINK]) lays out the thesis; this one stands on its own.
This is the arc of **Unit 4 of [The Workflow](https://git.jpaul.io/justin/ai-workflow-course)** — four modules that take the AI from "edits my files" to "operates in my world." MCP gives it hands. Skills teach those hands a playbook. Then we secure the whole thing, because the day you give an AI hands is the day a stranger's code can use them. And finally we point all of it at the hardest, most common target there is: a giant codebase you didn't write. If you're new here, the [first post](https://git.jpaul.io/justin/ai-workflow-course) lays out the thesis; this one stands on its own.
## MCP: the wall, and the way through it