Dan and Greg open with how agentic development has changed since the early days of Copilot. At the time, Greg was at GitHub, and he saw AI mostly help with boilerplate and editor completions. Cursor-style agents were the next widely-used advancement bringing session history and integrated team-wide practices. By June 2026, capable models and harnesses are common inside engineering teams, so the gap between teams increasingly comes from context engineering, repository structure, and whether old team shapes still align with the new ways of building software. For small teams and startups, the leverage of AI is a double-edged sword. Greg describes how SpecStory's original extensions required real sweat equity to reverse engineer chat-log formats across Cursor, Copilot, Claude Code, Amp, and other tools. Now, much of that surface can now be maintained by a fraction of one person's time. The danger is that easy MVPs can trick founders into believing they have validated a market. When the marginal cost of software falls, founders have to spend more of their scarce attention on demand, willingness to pay, distribution, and the routes to customers. The conversation turns to Greg's book, 25 Patterns in Agentic Engineering. He explains how he mined roughly 1,300 preserved SpecStory sessions and nearly 5,000 commits to extract durable patterns from his own agentic practice. Two patterns stand out. First, when code becomes free, verification becomes the bottleneck. Second, between agents turns, docs are the persistent API of the system. For Greg, as-built architecture documents are practical maps that let both humans and agents recover the shape of a subsystem without re-reading the entire codebase every time. Greg's development practice has changed accordingly. He favors trunk-based development and says his team uses almost no pull requests for everyday development, partly because agent-generated diffs arrive at a volume he does not want to review line by line. He prefers local agents over cloud agents that containerize the repo and open PRs later, because steering an agent while it runs keeps his mental model intact. Long unattended runs still make sense to him, but only when they start from a clear goal and a more detailed rider, with phased commits and verification points he can inspect after a walk or a night away. Dan and Greg also dig into coordination at larger scale. Greg is skeptical that issue trackers were ever clean or current enough to describe day-to-day engineering, but he sees issues becoming useful as specs with provenance and evidence that can be handed to agents. Personally, he runs several projects at once, usually three to five, with local agents in permissive modes, and rotates attention while long runs execute. That power is not free. He describes the dopamine loop of watching ideas come to life, the temptation to keep agents busy overnight, and the scarcity mindset created by subsidized access to frontier models. The episode closes with where Greg still does not trust the tools. Copywriting and visual design still require heavy human intervention because the models can blur rather than sharpen the message. He frames taste less as a mystical trait and more a selection amongst trade-offs and the ability to connect ideas in understandable ways. Coding has benefited from benchmarks and verifiable answers; much of the rest of the world is less tractable because there is no single ground truth for what "good" means. Full episode notes Click here to view the episode transcript. Chapters (00:00) - Introduction and guest background (00:55) - What agentic teams are running into (06:56) - Startup leverage, MVP traps, and maintaining SpecStory (09:26) - When software gets cheaper, distribution matters more (12:31) - Hand-written code, craft, and code as liability (16:21) - Mining 1,300 sessions into 25 patterns (19:01) - Verification and as-built architecture docs (23:55) - Co-writing docs with LLMs (25:15) - Keeping docs fresh through skills, Git, and verbose commits (27:50) - Trunk-based development for agentic teams (30:26) - Local steering versus cloud-agent pull requests (32:14) - Goal and rider plans, long runs, and Gas Town (35:52) - Replacing issue trackers with weekly docs (38:19) - Larger teams and issues as agent-ready specs (42:45) - Parallel projects and concentration limits (44:47) - Local agents, permissions, and risk judgment (46:57) - The cognitive pull of managing agents (51:58) - Scarcity, token costs, and model choice (58:57) - Copy, design, naming, and taste (01:05:04) - Why creative output resists verification (01:07:12) - Closing ⠀ Links from the show -------------------- Hardcore Agentic Engineering for builders who ship SpecStory Stoa 25 Patterns in Agentic Engineering AI Essentials for Tech Executives Meditations on Tech Beyond Code-Centric Goal Engineering WebRTC CRDT Trunk-based development Steve Yegge's Gas Town Dead Reckon Devin DORA Bear DeepSeek Qwen Yann LeCun ⠀ Guests ------- Greg Ceccarelli, Co-Founder & CPO, SpecStory Website Blog LinkedIn ⠀ Follow the podcast ------------------- LinkedIn Threads Instagram TikTok ⠀ Follow Dan Gerlanc ------------------- X LinkedIn Threads Bluesky
