Difficult tasks that are now easy – with Charles Delfs from Klai Studio

Charles and Matt discuss a working list of engineering problems that used to be hard in FileMaker and are now easy, plus the vocabulary you need to ask an agent for them.

Idempotency. Mutex. Message queues. Race conditions. Rich error objects. Test-driven development. None of it is new to computer science, and all of it is stuff FileMaker developers have been hand-solving for years without the words. Learn the words and you can prompt for the solution instead of letting the agent lead you.

Also: the difference between vibe coding and agentic engineering, why rage coding works (all caps included), and Matt's first public walkthrough of Pythia, his new amazing reporting tool.

⏱ CHAPTERS 0:00 What got easy, and Charles has not written code since November 2:15 Vibe coding vs agentic engineering, two competing definitions 5:40 The thing that used to be hard was research 6:40 Rage coding, FFS in all caps, and why it sometimes works 9:15 Build a v minus one. Refactoring is cheap now 12:20 Plan mode, and coding like jazz 13:30 Conditionals and feature gates as a JSON object 15:00 Defensive coding, and LLMs that guard too much 16:30 The senior engineer who asked for the temperature coefficient 17:30 Race conditions, defined for the rest of us 20:00 Test-driven development, and why FileMaker test suites were brutal 22:30 A free project idea: an OData-driven test suite for your scripts 24:45 Rich error objects, and the five word prompt that gets you one 27:45 Message queues, pipelines, throttling and debouncing 32:20 Idempotency: the blue button that sends two emails 39:03 Mutex, and how it differs from a transaction 42:35 The Dell sync bug that broke something every three days 47:12 Put an agent in your admin panel 52:22 What Klai is researching next: seeing into a huge codebase 53:30 Matt's adversarial agent loop: Claude Code, Hermes, and a message table 54:55 The API key vibe coded into the front end, and where governance fits 58:29 Pythia: reports that go past what FileMaker can do 60:02 22 apps on Fly.io for $13 a month 63:04 Function as a service, and keeping a light footprint

🎙 IN THIS EPISODE • Charles: vibe coding is building in a technology you cannot read or understand • Why FileMaker developers were never really vibe coding, and where that breaks down • The sunk cost fallacy is a human trait, not an AI one. Rip it out and start fresh • Feature flags as plain JSON keys, so accounting never clicks your reset button • Why the LLM's first version is probably better than your first version, and the second version is much better than your second • Rich errors carry a request ID, a suggestion, and a doc link, so an agent can debug them • Idempotency in FileMaker terms: that timestamp field you already add after the client complains • A sync bug at Dell that surfaced once every 20,000 transactions, and the week it took to find • Pythia syncs your data to DuckDB so a million records slice instantly, then writes the report code and hands you a PDF

🔗 LINKS Klai Studio: https://klai.studio Navarre.ai: https://navarre.ai Free weekly FileMaker AI classes: https://navarre.ai/#/classes Fly.io: https://fly.io

Coming in future episodes: code introspection research from Klai, and an episode on Genie with Bruno.

#FileMaker #Claris #AI #ClarisTalkAI #AgenticEngineering #VibeCoding