The Winchester Mystery House Problem in AI Development
Agentic Conversations (formally mlops.community)Show Notes
AI models are starting to act like appliances, locked into one narrow way of working, instead of the flexible infrastructure they used to be. Drew Breunig, an AI and data strategist working with the Overture Maps Foundation, joins us to explain why, and what it means for anyone building something that doesn't look like Claude Code.
Drew walks through his "Winchester Mystery House" idea: what happens once code gets so cheap to write that the only real bottleneck left is feedback. From there we dig into DSPy: signatures, the GEPA optimizer, and the brand-new Flex optimizer, which rewrites your code instead of just your prompt, complete with a real before-and-after on cost and accuracy. We also get into why so many AI-built apps and websites end up looking identical, the actual difference between an agent and a workflow, what Drew learned a year after shipping a code library with no code in it, and why he thinks the most valuable thing you can do right now is close the laptop and go talk to people.
CMPND: https://www.cmpnd.ai
Drew Breunig: https://www.linkedin.com/in/drewbreunig/ Demetrios: https://www.linkedin.com/in/dpbrinkm
Timestamps: [0:00] Cold open: when Claude Code tries to call itself [1:19] Biggest AI news: labs trading diversity for reliability [2:35] How harnesses get trained into models over time [5:41] The problem: your harness starts fighting the model [9:13] When do you need your own harness? [10:02] The Winchester Mystery House warning [16:13] The blank page problem: why everything looks the same [20:50] Infrastructure vs appliances: the thesis lands [22:40] Current tool loadout: GLM, Kimi, Claude Code, Pi [27:04] The Raspberry Pi personal agent running on Slack [31:00] Crystallizing tasks: when to replace AI with pure code [33:10] DSPy explained: separating what from how [35:23] How prompt optimizers actually work [39:31] DSPy pre-dates ChatGPT: model-agnostic programs [44:00] Why you still need to ship the code, not just the spec [50:00] Don't plan more than a month ahead anymore [54:00] Coaching agents all day feels productive — it isn't [57:58] The dopamine of building with agents vs. why you still need human feedback
More from Agentic Conversations (formally mlops.community)
What happens when you give 200 engineers who have barely touched AI a coding assistant and a six-month deadline to rebuild their platform? Pepijn Senders, a principal engineer who previously led AI enablement at HelloFresh, has done exactly that, and he chose Sonnet over Opus on purpose.
An AI slips out of its sandbox. A chatbot won’t explain your cat’s stripes. And your next shopping spree might not involve you clicking anything.
What happens to the web when the ones browsing it are no longer people? Sarah Drasner, Area Tech Lead at Google, sits down with us ahead of her Agentic Web keynote at AGNTCon + MCPCon North America. She works through that question from both directions: rebuild the web so agents can use it properly, or build agents smart enough to handle the web as it already exists.
Everyone is racing to build one agent that can do everything. Justin Schroeder, co-founder of Standard Agents, thinks the future looks more like thousands of tiny ones. Ahead of his talk on domain-specific agents at AGNTCon + MCPCon North America, he explains why tightly scoped agents might be the smarter bet, even if it feels like a step back toward the single-purpose machine learning models of a few years ago.
What happens to an MMORPG when half the players never log off? Issac Lee, who runs AI and blockchain experiments at NEXUS, has been testing that idea. His team is filling game worlds with agent players instead of scripted NPCs, so a new title feels alive from day one.