On Zoom, Tuesdays at 10 AM PST - an hour of live coding, Q&A, and production-ready AI engineering
Tuesday, June 16, 2026 at 10 AM PST
We've talked a lot about design discussions for planning work with AI and getting leverage before writing the code, but this process has a common pitfall: it combines product decisions (how does it work, what is the user experience) with technical decisions (how do we build it, what patterns do we follow).
This complecting of concerns can cause important questions to be missed. On today's AI that works we'll dig into techniques to split out product vs. technical questions to enable less-technical folks to participate in product specification that is grounded in codebase research, and ensure technical depth is achieved without getting distracted by product questions.
Weekly conversations with @hellovai & @dexhorthy about getting the most juice out of today's models
When: Every Tuesday at 10 AM PST on Zoom
Duration: 1 hour of live coding, Q&A, and production-ready insights
Goal: Take your AI app from demo → production
Let's code together.
Before joining, get familiar with our toolkit:
| ### **Core Tools** - **Zoom** - Live sessions - **Cursor** - AI-powered IDE - **Git** - Version control - **Claude Code** - Agentic Coding - **CodeLayer** - Agentic Coding Tool | ### **Languages** - **Python/TypeScript/Go** - Application logic - **BAML** - Prompting DSL - [Repository](https://github.com/boundaryml/baml) - [Getting Started Guide](https://gloochat.notion.site/benefits-of-baml) | ### **Package Managers** - **Python:** [UV](https://docs.astral.sh/uv/getting-started/installation) - **TypeScript:** PNPM - **Go:** Go modules |
From Demo to Production - One Episode at a Time
| 📅 Episode | 📝 Description |
|---|---|
| UPCOMING 2026-06-16 #62: Product Specs with AI code • register | We've talked a lot about design discussions for planning work with AI and getting leverage before writing the code, but this process has a common pitfall: it combines product decisions (how does it work, what is the user experience) with technical decisions (how do we build it, what patterns do we follow). This complecting of concerns can cause important questions to be missed. On today's AI that works we'll dig into techniques to split out product vs. technical questions to enable less-technical folks to participate in product specification that is grounded in codebase research, and ensure technical depth is achieved without getting distracted by product questions. |
| PAST 2026-06-09 #61: Hands-on with Fable 5 watch • code | We had agent observability on the schedule, but Anthropic shipped Fable 5 about twenty minutes before we went live, so we tossed the plan and got hands-on with the new model instead. Zero prep, all live. This is an unscripted look at exactly how we kick the tires on a fresh model release: take the hardest problem you're already deep in, hand it over, and watch whether it finds leverage you didn't. Vaibhav ran it against an in-progress design doc for the BAML VM's observability layer, Dex ran it against an old race-condition benchmark he keeps around, and we talk through what the model caught, what it missed, and why most model releases are more hype than the value they deliver day to day. |
| PAST 2026-06-02 #60: How to Build AI Agents that Work in Any Language watch • code | In this episode, we discuss the challenge of building multilingual AI applications that perform consistently whether your user is interacting in English, Spanish, French, whatever. Can you simply run an English prompt through a basic translator? Or will that break down in production? We'll be breaking down practical engineering strategies for designing flexible, cross-lingual prompt architectures that maintain semantic alignment without forcing you to build and manage separate pipelines for every language. |
| PAST 2026-05-26 #59: No Vibes Allowed: Performance Engineering code | This week on the podcast, we are doing another no vibes allowed episode focusing on performance engineering. We will dive into high-performance engineering on virtual machines to help you maximize efficiency out of your compute infrastructure. When you are deploying heavy LLM workloads or complex pipelines, an unoptimized VM can lead to crippling latency, memory bottlenecks, and ballooning costs that break your application in the real world. We break down practical techniques to configure your environments, manage resources, and eliminate overhead so your models run flawlessly under pressure. |
| PAST 2026-05-19 #58: How AI Agents Can Safely Ship Code to Production watch • code | This week, the top headline is vibe coders realizing that they can use feature flags to ship experimental (read: slop) features to production without impacting all customers. Shipping code is a lot harder when everything is changing all the time. Feature flags can be a good technique to test various things, but how do you set that up? Do you feature flag new models? New prompts? New harnesses? We'll dive into details here and see where feature flags improve your product delivery vs. just giving you an excuse to ship more slop. |
| PAST 2026-05-12 #57: "Code Mode" Deep Dive watch • code | On Monday, Pash from OpenAI shared that Codex has a secret "code mode" feature - an alternative to traditional tool calling. There's a lot of debate going on around the best way to give tools to models - skills vs. mcps, CLIs and bash vs custom tools, or letting the model write code for everything. In this episode we're going to cut through the hype and dive deep on the differences and tradeoffs between these methods. • What is "code mode" and how does it work • Tradeoffs between MCP vs. Bash+CLI vs. Code mode • Why it matters to agent or harness builders |
| PAST 2026-05-05 #56: OpenAI tells you not to build your own harness watch • code | Harness engineering is all the hype now, so on this week on the podcast we're looking back to an article written by OpenAI in February about harness engineering, "Harness engineering: leveraging Codex in an agent-first world". In this article, they claim that the era of "hand-written code" is officially over. We break down their experiment of shipping a million-line product with zero manual coding, shifting the human role from "coder" to "environment designer." |
| PAST 2026-04-28 #55: No Vibes Allowed - Building Design Docs with AI watch • code | In this month's no vibes allowed episode, Vaibhav will show how he uses AI to make design docs for complicated tasks by building out an actual design doc for a feature in BAML. As always for our no vibes allowed series, we will be solving real problems in real production systems. |
| PAST |
$ claude mcp add ai-that-works \
-- python -m otcore.mcp_server <graph>