Claude Code

February 10

45 mins

Episode Description

What we cover

What Claude Code is (and why it’s useful even if you’re not an engineer)
The real difference between Claude in the browser vs. Claude Code on your machine
Using /init and Claude MD files to shape behavior and context
The “treat it like an intern” model: limiting access and building a walled garden
Why task management is a great first use case (easy to validate + fast feedback loops)
Exporting calendar windows vs. connecting Claude directly to your calendar
Switching models for speed: when Haiku is “good enough” and when you need more
When Claude Code spirals on web tasks (and how to debug it by asking: “What are you doing?”)
Content retrieval as a killer workflow: “Where have I talked about this before?”
Building reusable workflows: slash commands, sub-agents, hooks, and plugins
Teresa’s publishing stack: titles, descriptions, show notes, chapters from transcripts
Fact-checking workflows: validating claims against transcripts and research sources
Using Claude for audience analytics and content prioritization (with caveats)
A deep nerdy detour: Zettelkasten-style research and using Claude to improve rigor

Memorable moments / quotes (paraphrased)

Petra’s metaphor: Claude Code is like a dog—sometimes it returns with the stick, sometimes it gets lost in the woods.
The “intern” framing: don’t hand Claude the whole company on day one—scope access intentionally.
Teresa’s output jump: more writing volume without (in her view) losing quality—because the workflow scaffolding got better.

Resources & Links:

Mentioned in this episode: