Skip to content

Commit 6640402

Browse files
committed
AI generated ack
1 parent 8ebbb91 commit 6640402

File tree

13 files changed

+37
-20
lines changed

13 files changed

+37
-20
lines changed

scripts/generate-podcast.js

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,13 @@ async function generateDialogue(content, fileName) {
108108

109109
const model = genAI.getGenerativeModel({ model: DIALOGUE_MODEL });
110110

111+
// Special handling for intro.md - add self-aware meta-commentary
112+
const isIntro = fileName === 'intro';
113+
const metaCommentary = isIntro ? `
114+
115+
SPECIAL INSTRUCTIONS FOR THIS EPISODE:
116+
This is the course introduction. When discussing the section about how the course was developed using AI (including the podcast itself), have Alex and Sam briefly acknowledge in a natural, professional way that they themselves are AI-generated voices. This should feel like a thoughtful meta-moment, not gimmicky. Keep it concise - one or two exchanges where they note the self-referential nature of AI-generated hosts discussing AI-generated content. Make it feel authentic to how senior engineers would react to this realization.` : '';
117+
111118
const prompt = `You are converting technical course content into a natural, engaging two-person podcast conversation.
112119
113120
Speakers:
@@ -122,7 +129,7 @@ Guidelines:
122129
- Keep technical accuracy - don't dumb down the content
123130
- Make it engaging but professional
124131
- Break down complex concepts through dialogue
125-
- Reference real-world scenarios and examples
132+
- Reference real-world scenarios and examples${metaCommentary}
126133
127134
Technical Content Title: ${fileName}
128135

website/docs/intro.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,9 +64,19 @@ Most importantly: you'll know **when to use agents** and **when to write code yo
6464
## Prerequisites
6565

6666
- **Experience:** 3+ years professional software engineering
67-
- **Tools:** Access to a CLI coding agent (Claude Code, Aider, Cursor, or similar)
67+
- **Tools:** Access to a CLI coding agent (Claude Code, OpenAI Codex, Copilot CLI, etc)
6868
- **Mindset:** Willingness to unlearn "AI as teammate" and adopt "AI as tool"
6969

70+
## About This Course's Development
71+
72+
**This course practices what it teaches.** The entire curriculum—content structure, lesson progression, code examples, and documentation—was developed using the same AI-assisted techniques and workflows you'll learn here.
73+
74+
Every module was planned, researched, drafted, and refined through systematic prompting, agentic research, and iterative validation. The process followed the exact methodology outlined in the course: breaking work into agent-appropriate tasks, grounding in architectural context, and validating output critically.
75+
76+
**The podcast version of each lesson** was generated using Claude Code and Google's Gemini API—converting technical content into conversational dialogue, then synthesizing multi-speaker audio. The voices you hear (Alex and Sam) are AI-generated, as is their script. Even this acknowledgment exists because we applied the principle of transparency in AI-assisted work.
77+
78+
This isn't marketing. It's validation. If these techniques can produce production-grade training material on their own application, they're robust enough for your codebase.
79+
7080
---
7181

7282
**Ready to start?** Begin with [Understanding the Tools](/docs/understanding-the-tools/lesson-1-intro).

0 commit comments

Comments
 (0)