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

- 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:
2026-06-22 19:15:20 -04:00
parent e5960c17ab
commit 250189a60e
18 changed files with 41 additions and 37 deletions
+1 -1
View File
@@ -12,7 +12,7 @@ Tags: AI, CI/CD, testing, security scanning, containers, secrets,
Here's a thing that should worry you a little more than it does: AI is *fast*, and most of what makes it fast also makes it dangerous. It writes a function in three seconds. It also writes a *wrong* function in three seconds, one that reads beautifully, uses the right names, follows your conventions, and ships a flipped comparison you'll never catch by skimming. The generation got cheap. The *catching* didn't — unless you make it.
That's this whole unit, and it's the post where [The Workflow]([COURSE LINK]) shifts gears. The first half of the course was about getting out of the chat window and making your work shareable and recoverable — Git as undo for the AI, hosting, review. Useful, foundational, a little slow-burn. This is where it speeds up. Seven modules, one job: **build the machine that checks AI's work and ships it, automatically, so AI's speed becomes shipped software instead of shipped risk.**
That's this whole unit, and it's the post where [The Workflow](https://git.jpaul.io/justin/ai-workflow-course) shifts gears. The first half of the course was about getting out of the chat window and making your work shareable and recoverable — Git as undo for the AI, hosting, review. Useful, foundational, a little slow-burn. This is where it speeds up. Seven modules, one job: **build the machine that checks AI's work and ships it, automatically, so AI's speed becomes shipped software instead of shipped risk.**
If you run infrastructure for a living, the punchline lands early and it lands hard, so I'll spoil it now: by the end of this unit you own a pipeline end to end. Tests, gates, containers, deploys, and the actual compute underneath. Not "I use someone's CI." *Yours.* Let me walk the arc.