Discover
Free Form AI
Free Form AI
Author: Michael Berk
Subscribed: 1Played: 0Subscribe
Share
© 2026 Michael Berk
Description
Free Form AI is a builder-led podcast that explores the ever changing landscape of machine learning and artificial intelligence. We pressure-test ideas live and uncover what matters before it’s obvious, covering topics ranging from cutting-edge implementations to the philosophies of product development. Whether you're an engineer, researcher, or enthusiast, join us for practical takeaways to navigate the ever-changing world of AI.
53 Episodes
Reverse
Being technically right doesn't mean anyone understands you. In Episode 53 of Free Form AI, Michael Berk and Ben Wilson break down how engineers can communicate complex technical ideas to nontechnical stakeholders, explain uncertainty, and make sure their message actually lands.We discuss how to present data without misleading people, why trusted experts need to question their own assumptions, and how asking better questions helps verify understanding. Good technical communication isn't about sounding smart. It's about giving people the information they need to make better decisions.00:00 — Communicating with nontechnical stakeholders02:44 — Explaining data, uncertainty, and misleading charts05:01 — The purpose of communication12:00 — Why trusted experts need more scrutiny18:16 — Checking understanding and explaining complex systems
AI makes it dramatically faster to build software. It also makes it easier to build the wrong thing. In this episode, we break down the product development lifecycle from defining the right problem to designing, testing, and driving adoption, including why teams should actively try to invalidate their own ideas, where Gen AI creates false confidence, and what actually limits product development when implementation gets cheap.00:00 — Why Gen AI can make product development worse05:00 — Defining the problem before building the solution16:30 — What actually limits good product design25:30 — Getting users to adopt what you build47:00 — The four risks every product should test earlyAI can make your team four times faster at implementation. That only matters if you’re building something worth implementing.
Four years at Databricks produced eight career lessons. Now Ben gets to challenge them. We dig into why humility makes you more effective, how “make them tell you no” can create career opportunities, why understanding the problem matters more as AI gets better at implementation, and how systems, visibility, curiosity, and personal brand shape long-term career growth.00:00 — Why you’re less important than you think08:00 — Ask for forgiveness, not permission17:45 — Spend more time understanding the problem24:25 — Impact, visibility, and choosing the right work36:10 — Systems, career growth, personal brand, and curiosityThe common thread across all eight lessons: careers compound when you stay curious, create opportunities instead of waiting for them, and understand the systems around you well enough to change them.
Fifty episodes into Free Form AI, we’re looking back at what actually changed our minds. We break down five lessons on why predicting AI is nearly impossible, how sharing unfinished ideas makes them better, why unexpected connections and analogies are powerful tools for learning, and how much control you actually have over your career and workplace culture.00:00 — Why predicting AI is nearly impossible07:00 — Why putting unfinished ideas in the open makes them better12:30 — Finding useful connections between unrelated ideas18:45 — Why analogies make technical ideas stick33:00 — Changing bad workplace culture, or knowing when to leaveAfter 50 episodes, the biggest lesson might be simple: good ideas rarely arrive fully formed. You find them by exploring, debating, teaching, failing, and changing your mind.
Writing a technical book sounds great until you learn what it actually takes. In this episode, Ben breaks down his experience writing Machine Learning Engineering in Action, from pitching and rewriting chapters to technical reviews, royalties, and spending up to 60 hours a week on the process. We also get into whether publishing a tech book actually helps your career, why writing forces you to understand a subject deeply, and the communication lessons that make technical ideas stick.00:00 — How a technical book goes from idea to manuscript11:00 — Why chapters can require dozens of rewrites16:00 — What writing a book teaches you about communication27:00 — The editing and publishing process32:00 — Royalties, career value, and whether it’s worth itA tech book can build credibility and force you to master your subject. Just don’t expect it to be an easy way to make money.




