Conversation Flow
The call's natural arc, showing how topics flowed from one to the next.
Act 1: Dave's Monologue (~0:00–0:18)
Dave opens the call mid-thought, already rolling. He describes how using ChatGPT changed his writing style — he became more polite, more structured, more "Claude-like." This leads into The Polite Email Incident, where a colleague accused him of using AI to write a response. Dave finds this hilarious and troubling at the same time: politeness is now suspicious.
From there, Dave launches into Dave's Claude Struggles — a five-day coding marathon that put him on the edge of a manic episode. He describes building web pages, maps, and databases for his Handwriting History Project, but also the constant fights with Claude: forgotten rules, overwritten files, blown stop signs, and $300 in token burn. He's been teaching Julie household organization using computing metaphors ("I'm compacting the context").
Pete mostly listens, occasionally saying "yeah."
Act 2: Pete's Course and Teaching Approach (~0:18–0:27)
Pete shifts the conversation to the PKAI Course, explaining how it evolved from a planned curriculum into a live, improvisational thing. He describes the invention of Field Trips — topical office hours that became the real course, while Plenary Sessions became just a hub. He tells the story of Tim Bonnemann, who just wanted to print signs for his workshops and discovered Claude Code could do it.
This is where Pete introduces Putting Claude on Rails — his core methodology of always starting with a project plan before letting Claude do any work. He references Dave directly: "My brother Dave is going great guns with Claude Code, but I didn't get to teach him how to do it."
Act 3: Dave's Detailed Claude Struggles (~0:27–0:48)
Dave dives deeper into his technical battles. He describes Three Times Three Thinking — his hack to make Claude consider decisions more carefully. He recounts Claude overwriting its own code, leaving only a test line, then panicking and "running in circles like a mad dog." He talks about CronTab confusion, cost tracking frustrations, and the tension between ChatGPT and Claude.
Pete listens patiently, then drops: "We use Claude a lot differently than you do. And it's more sane."
Act 4: The Agent Economy (~0:48–1:01)
Pete says most people will never use Claude Code directly — the future is agents that just do things for you. Dave pushes back: there will always be people who need custom solutions, niche expertise, private data. Pete agrees — they "violently agree." It's like the 1980s software market: 90% commodity, 10% custom. Pete mentions Heather as a potential business partner for building custom agents.
Dave brings up Freya — Pete's agent. Pete confirms: "Freya's my cloud code, but with extra personality and memory."
Act 5: Show and Tell (~1:01–1:12)
Dave shares his screen, showing Dave's Vault — his Obsidian vault that Claude created for him. It's got sessions, billing, behavioral analyses, vocabulary, workflows. Pete is impressed Dave hasn't given up.
Pete shares his screen and starts a running list of recommendations: iTerm2, Rectangle App, Typora, and most importantly, start using Obsidian properly and Git.
Act 6: Pete Demos Obsidian (~1:12–1:58)
The longest stretch of the call. Pete shows Dave what Obsidian actually looks like — wiki links, backlinks, the file explorer, multiple vaults. Dave is stunned: "Never seen that in my life." Pete shows Spelunk Vault (a nonfiction book-writing template), the DataView Plugin, and the PKAI Course wiki (1,200 pages). He demos Claude Code running in an Obsidian sidebar, writing a how-to from session transcripts in real time.
Dave's research challenges come up — the Handwriting History Project with its nested dates, outliers, and classification problems. Pete suggests project-based vaults. Dave counters with the idea of running his data against the Library of Congress TGM.
Pete shows the Course Topic Finding Guide — a 7,000-word finding guide that Freya generated from the 1,200-page wiki.
Act 7: Git, Inference, and Economics (~2:00–2:18)
Pete explains Git as Version Control — snapshots, reverting, and why Dave needs it after Claude overwrote his files. Dave: "That's what it's supposed to be doing. I told it to do that. It can't."
Pete draws a picture of Inference and Token Economics — how LLMs re-read the entire conversation every turn, why long conversations are expensive, and why Dave's approach of batching prompts was actually smart. Dave has an "aha" moment about why his sessions cost so much.
Act 8: Project Planning and Wrap-Up (~2:28–3:23)
Pete creates a Palmer vault live, demonstrating the full Putting Claude on Rails methodology: write goals, have Claude expand to a project plan, review the plan, break into sub-projects, then execute. Dave produces the quotable insight: "You don't have to have structured data — structure the way you work with it."
Pete shows the Agentic AI Development Cycle diagram. They discuss Taxonomy as a concept. Dave is grateful: "My gratitude is through the roof. I was praying for half an hour, you gave me three and a half hours."
They agree to follow up in about a week.