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

style(no-slop): remove em-dashes + banned words from syllabus and blog

Browse Source 
Apply the no-ai-slop standard to the two remaining reader-facing surfaces:
- the-workflow-syllabus.md: 91 em-dashes -> 0 (all content preserved; headers
  normalized to periods/colons, en-dash ranges kept).
- blog/ (17 posts + README): 670+ em-dashes -> 0, banned words removed. Filled
  course URLs and [insert a screenshot] placeholders preserved; blog voice intact.

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-23 07:28:54 -04:00
parent 66c15800c3
commit a670ccbc8b
19 changed files with 622 additions and 622 deletions
Download Patch File Download Diff File Expand all files Collapse all files
blog/01-announcing-the-workflow.md
+16 -16
View File
@@ -14,13 +14,13 @@ Let me start with the uncomfortable part: the AI is doing its job. You open a ch
So why does building anything real with it still feel like herding cats?
I've spent the last while watching a lot of smart IT people — folks who can stand up a cluster, automate a pipeline, troubleshoot a gnarly auth problem at 2am — hit the same wall the moment they try to build actual software with AI. And it's almost never the model's fault. The model is fine. What's failing them is *everything around* the code.
I've spent the last while watching a lot of smart IT people (folks who can stand up a cluster, automate a pipeline, troubleshoot a gnarly auth problem at 2am) hit the same wall the moment they try to build actual software with AI. And it's almost never the model's fault. The model is fine. What's failing them is *everything around* the code.
That gap is what I built a course about. It's called **The Workflow**, it's free, and this post is me telling you it exists and why I think it's worth your time.
## The loop you're probably in
Here's the workflow almost everyone starts with, and — I want to be fair here — it genuinely works for a while:
Here's the workflow almost everyone starts with, and, I want to be fair here, it genuinely works for a while:
1. Describe what you want in a chat window.
2. The AI gives you code.
@@ -32,7 +32,7 @@ Here's the workflow almost everyone starts with, and — I want to be fair here
For a single file you're poking at for an afternoon, this is great. I'm not going to tell you to over-engineer a five-line script. But the loop falls apart the second your project grows along either of the two axes every real project grows on: **more than one file, and more than one day.**
The moment you have a second file, *you* become the integration layer — hand-merging blobs of text between a chat tab and your disk, hoping you didn't drop a function in the shuffle. The moment you come back the next day, the AI's memory of what you decided yesterday is just… gone. And the quiet, dangerous one: when the AI confidently makes a mess — deletes a function you needed, "refactors" something into a subtly broken state — what's your recovery plan? For most people right now it's *Ctrl-Z until it looks right*, or retyping from memory. That's high-wire work with no net.
The moment you have a second file, *you* become the integration layer, hand-merging blobs of text between a chat tab and your disk, hoping you didn't drop a function in the shuffle. The moment you come back the next day, the AI's memory of what you decided yesterday is just… gone. And the quiet, dangerous one: when the AI confidently makes a mess (deletes a function you needed, "refactors" something into a subtly broken state), what's your recovery plan? For most people right now it's *Ctrl-Z until it looks right*, or retyping from memory. That's high-wire work with no net.
None of those three problems are about how smart the model is. A better model writes better code; it still doesn't give you a record of what changed, a way to undo a mess, or a memory that survives a closed tab. Those come from the engineering scaffolding *around* the model.
@@ -42,33 +42,33 @@ Here's the line the whole course hangs on, and I'll be honest, it's the thing I
> **The model is the cheap, swappable part. The workflow around it is the skill that lasts.**
Think about how many models you've already churned through. The one you're using today will be replaced — probably by something cheaper and better — and when it is, your prompts mostly carry over and your *habits* fully carry over. Version-control discipline, the review reflex, a CI pipeline, the instinct to hand an agent a branch instead of your whole repo — none of that depends on which model you run. You learn it once and it pays out across every model you'll ever touch.
Think about how many models you've already churned through. The one you're using today will be replaced, probably by something cheaper and better, and when it is, your prompts mostly carry over and your *habits* fully carry over. Version-control discipline, the review reflex, a CI pipeline, the instinct to hand an agent a branch instead of your whole repo: none of that depends on which model you run. You learn it once and it pays out across every model you'll ever touch.
That's why the course is deliberately model- and vendor-agnostic. I'm not here to sell you on a particular AI. Whichever LLM you use, the scaffolding is the same — and the scaffolding is the part that doesn't expire.
That's why the course is deliberately model- and vendor-agnostic. I'm not here to sell you on a particular AI. Whichever LLM you use, the scaffolding is the same, and the scaffolding is the part that doesn't expire.
[insert a screenshot referencing the course README / thesis here]
## What's actually in it
It's 27 modules plus a capstone, built as a **dependency chain, not a topic list** — every module assumes only what the previous ones taught, and nothing references a tool before it's been introduced. It groups into five units:
It's 27 modules plus a capstone, built as a **dependency chain, not a topic list**. Every module assumes only what the previous ones taught, and nothing references a tool before it's been introduced. It groups into five units:
- **Unit 1 — Get out of the chat window.** The local foundation: version control as *undo for the AI*, getting the AI editing real files safely, and committing the AI's config so your setup is a durable artifact.
- **Unit 2 — Make it shareable, reviewable, recoverable.** The team layer: hosting and remotes, issues, reviewing code you didn't write (one of the most important and least-taught skills in this whole space), collaboration, and recovery when it goes wrong.
- **Unit 3 — Automate the checking and shipping.** The pipeline: testing, CI, security scanning for AI-generated code, containers, secrets, delivery, and the runners underneath it all.
- **Unit 4 — Extend the AI into your systems.** The frontier: MCP servers, skills, securing the third-party ones, and pointing AI at a big codebase you *didn't* write.
- **Unit 5 — AI in the loop.** Agents operating *inside* the pipeline, from assistive (it helps, you decide) to autonomous (it acts, supervised), plus the evals that make trusting them possible.
- **Unit 1, Get out of the chat window.** The local foundation: version control as *undo for the AI*, getting the AI editing real files safely, and committing the AI's config so your setup is a durable artifact.
- **Unit 2, Make it shareable, reviewable, recoverable.** The team layer: hosting and remotes, issues, reviewing code you didn't write (one of the most important and least-taught skills in this whole space), collaboration, and recovery when it goes wrong.
- **Unit 3, Automate the checking and shipping.** The pipeline: testing, CI, security scanning for AI-generated code, containers, secrets, delivery, and the runners underneath it all.
- **Unit 4, Extend the AI into your systems.** The frontier: MCP servers, skills, securing the third-party ones, and pointing AI at a big codebase you *didn't* write.
- **Unit 5, AI in the loop.** Agents operating *inside* the pipeline, from assistive (it helps, you decide) to autonomous (it acts, supervised), plus the evals that make trusting them possible.
Then a capstone that takes one real feature end to end — prompt → branch → AI implementation → tests → PR → CI → security scan → review → merge → deploy — so it all clicks into a single motion instead of a pile of tips.
Then a capstone that takes one real feature end to end (prompt → branch → AI implementation → tests → PR → CI → security scan → review → merge → deploy) so it all clicks into a single motion instead of a pile of tips.
Every module is a written lesson you read *and* a lab you run at your own keyboard, on your own machine, any OS. No quizzes, no certificates, no grading — each one ends at a concrete "you're done when…" check. And it leans on a tiny running example app the whole way through, so you're always working on something real.
Every module is a written lesson you read *and* a lab you run at your own keyboard, on your own machine, any OS. No quizzes, no certificates, no grading; each one ends at a concrete "you're done when…" check. And it leans on a tiny running example app the whole way through, so you're always working on something real.
## Who this is for (and who it isn't)
This is for IT professionals who are already fluent in an AI chat window and comfortable with ops concepts. If you paste code between a chat tab and your editor and feel the friction, you are exactly the audience.
It is **not** a beginner course. I'm not going to teach you what a variable is. I'm going to teach you the engineering scaffolding that makes AI-assisted work safe, shareable, and repeatable — the stuff a generic "intro to developer tools" course covers, except reframed around the fact that *AI changes the cost-benefit of every tool in it*, and usually makes the tool more valuable, not less.
It is **not** a beginner course. I'm not going to teach you what a variable is. I'm going to teach you the engineering scaffolding that makes AI-assisted work safe, shareable, and repeatable: the stuff a generic "intro to developer tools" course covers, except reframed around the fact that *AI changes the cost-benefit of every tool in it*, and usually makes the tool more valuable, not less.
One more bit of honesty, because that's how I like to write: the early modules won't make you faster. Setup rarely does. The payoff compounds over the next several modules. If it feels like overhead at first, that's expected — and it's the same deal as every good piece of infrastructure you've ever stood up.
One more bit of honesty, because that's how I like to write: the early modules won't make you faster. Setup rarely does. The payoff compounds over the next several modules. If it feels like overhead at first, that's expected, and it's the same deal as every good piece of infrastructure you've ever stood up.
## Start here
@@ -76,4 +76,4 @@ The course is free and lives here: **https://git.jpaul.io/justin/ai-workflow-cou
Over the next few weeks I'm going to walk through it here on the blog, roughly a post per module, so you can follow along even if you never clone the repo. Next up: the copy-paste problem in detail, and how to get your workspace set up to fix it.
If you've felt this exact friction — or if you think I've got the thesis wrong — I genuinely want to hear it. Drop a comment below.
If you've felt this exact friction, or if you think I've got the thesis wrong, I genuinely want to hear it. Drop a comment below.