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

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

Browse Source 
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:
Claude (agent)
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
Download Patch File Download Diff File Expand all files Collapse all files
blog/11-reviewing-code-you-didnt-write.md
+1 -1
View File
@@ -14,7 +14,7 @@ Here's a thing I had to unlearn the hard way: I'd spent years using how *clean*
Then I started reviewing code an AI wrote, and that instinct walked me straight into a wall.
This is the eleventh post in my walk through [The Workflow]([COURSE LINK]), my free course on the toolchain *around* AI coding. And I'll say this plainly, the way the course does: reviewing a diff you didn't write is one of the most important and least-taught skills in this whole space. If you take one habit from the entire series, I'd be tempted to point at this one. So this post gets the weight it deserves.
This is the eleventh post in my walk through [The Workflow](https://git.jpaul.io/justin/ai-workflow-course), my free course on the toolchain *around* AI coding. And I'll say this plainly, the way the course does: reviewing a diff you didn't write is one of the most important and least-taught skills in this whole space. If you take one habit from the entire series, I'd be tempted to point at this one. So this post gets the weight it deserves.
## Why your review instinct is now lying to you