Where can I listen to this podcast?

This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.

Does this podcast accept guests?

Yes, this podcast regularly features guests.

BEAM There, Done That

Claim This Podcast

by Plangora

4.3(4 reviews)

14 episodes

Updated Daily

Accepts GuestsHas Sponsors

Podcast Overview

BEAM There, Done That is a podcast about building real systems with Elixir, Erlang, and the BEAM. We’ve built it before — distributed systems, fault‑tolerant services, event pipelines, real‑time apps, production nightmares, and the supervision trees that saved them. Each episode dives into practical lessons from shipping software on the BEAM: architecture decisions, scaling challenges, operational failures, and the patterns that actually work. No hype. No theory without scars. Just hard‑won experience from engineers who’ve been there.

Language

🇺🇲

Publishing Since

2/27/2026

Visit Website View on Apple Podcasts RSS Feed

1 verified contact email on file for BEAM There, Done That

Pitch yourself as a guest, propose sponsorships, or reach out directly to the host.

See contact details

Recent Episodes

June 5, 2026

Who Builds the Next Generation of Senior Devs? Bruce Tate on AI, Juniors, and the Career Path Crisis

The dashboards are green. PRs are shipping faster than ever. So why are seniors quietly burning out — and juniors not actually learning?In this episode, Allen Wyma and Francesco Cesarini sit down in person with Bruce Tate — author of Seven Languages in Seven Weeks, co-author of 10+ books on Elixir, and founder of Groxio — who just shut down a 10-year mentoring organization because the junior developer career path had become too unclear to sustain.Topics include:<ul><li>why AI has broken the traditional apprenticeship model without replacing it</li><li>three scenes from a Tuesday afternoon: Freddie the junior, Martin the senior, and the manager watching the green dashboard — what each is missing about the other two</li><li>the five modes of AI-assisted coding (completion, mini tasks, debugging, collaboration, vibing) and which ones a junior should actually live in</li><li>why the pull request is no longer a learning moment — and what to do instead</li><li>the four things a junior must develop to become a senior in 2026</li><li>what leadership owes the next generation, and the one pledge every team should make</li><li>where BEAM languages fit in all of this — and why Elixir may be the best language for AI-assisted development</li></ul>The productivity dividend is real. The question is whether we invest it or eat it.Resources mentioned:<ul><li>Groxio: grox.io</li><li>Tidewave</li><li>Ash Framework</li><li>"Tell Me a Story" talk by Sasha (referenced in episode)</li></ul>Recorded May 18, 2026.

May 29, 2026

AI Found 5 CVEs in One Afternoon — The BEAM Security Wake-Up Call | Peter Ullrich & Jonathan Machen

The BEAM ecosystem spent decades flying under the radar - too niche to attract serious attackers. That era is over.In this episode, we sit down with Peter Ullrich, the developer who ran a $10 experiment at ElixirConf EU in Málaga and discovered a vulnerability that could crash the BEAM with a 13-character string - with zero prior security experience. Then we hear from Jonathan Machen, CISO of the Erlang Ecosystem Foundation, whose job is to catch and coordinate everything Peter finds.We cover:<ul><li>How Peter built a simple bash script that scanned the most-downloaded Hex packages - and what he found</li><li>Why LLMs have changed the cost and skill floor for vulnerability research forever</li><li>The CVE disclosure process: what happens from the moment a bug is found to the moment it's published</li><li>How the EEF's CNA went from 9 CVEs in a year to more in a single week</li><li>What library maintainers should do right now (spoiler: it's three clicks on GitHub)</li><li>The AGES initiative, supply chain security, and the gap between what's been built and what the moment demands</li><li>Why paying a vendor like Trivy isn't enough - and what actually needs to happen</li></ul>If you run Phoenix in production, this episode is required listening.Resources mentioned:<ul><li>Peter's blog post and prompts: github.com/pultrich (linked in post)</li><li>Linux Foundation's Scrutineer project</li><li>Report vulnerabilities: cna@erlef.org</li><li>Support the Erlang Ecosystem Foundation: erlef.org</li></ul>

May 22, 2026

Inside the BEAM: Björn Gustavsson on Maps, Records, and Runtime Design

For the first time in over a decade, the Erlang runtime is gaining a new native data type — and on this episode of BEAM There, Done That, hosts Francesco Cesarini and Allan Wyma sit down with Björn Gustavsson, known by many as the “B” in BEAM. Björn takes listeners deep into the history of records, maps, tag bits, and the architectural trade-offs that shaped the Erlang runtime from the 1990s to today. The discussion explores why records were originally implemented as a hack, why maps never fully replaced them, and what finally made native records possible after nearly 30 years. Along the way, the episode becomes a rare tour through BEAM internals, compiler design, runtime tagging, and the practical realities of evolving a production VM used at massive scale. If you care about language design, runtime systems, or the history and future of Erlang/OTP, this is one of the deepest technical conversations the podcast has released.

14 total episodes available

Similar Podcasts

Discover related shows you might enjoy

Thinking Elixir Podcast

ThinkingElixir.com

Elixir Wizards

SmartLogic LLC

The Pragmatic Engineer Podcast

Gergely Orosz

Oxide and Friends

Oxide Computer Company

CoRecursive: Coding Stories

Adam Gordon Bell - Software Developer

Accidental Tech Podcast

Marco Arment, Casey Liss, John Siracusa

Kubernetes Podcast from Google

Abdel Sghiouar, Kaslin Fields

Pivot

New York Magazine

Late Night Linux

The Late Night Linux Family

The Vergecast

The Verge

Syntax - Tasty Web Development Treats

Wes Bos & Scott Tolinski - Full Stack JavaScript Web Developers

Better Offline

Cool Zone Media and iHeartPodcasts

Prof G Markets

Vox Media Podcast Network

All-In with Chamath, Jason, Sacks & Friedberg

All-In Podcast, LLC

The Foreign Affairs Interview

Foreign Affairs Magazine

Deep-dive analytics for BEAM There, Done That

Frequently asked questions

Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.

What is BEAM There, Done That?: BEAM There, Done That is a podcast about building real systems with Elixir, Erlang, and the BEAM.

We’ve built it before — distributed systems, fault‑tolerant services, event pipelines, real‑time apps, production nightmares, and the supervision trees that saved them.

Each episode dives into practical lessons from shipping software on the BEAM: architecture decisions, scaling challenges, operational failures, and the patterns that actually work.

No hype. No theory without scars. Just hard‑won experience from engineers who’ve been there.
How often does this podcast release new episodes?: This podcast updates daily.
Where can I listen to this podcast?: This podcast is available on 4 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.
Does this podcast accept guests?: Yes, this podcast regularly features guests.

Legal Disclaimer

Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.

All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.

We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.

While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.

By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.