116: Jerod Santo - Building the Changelog Platform with Elixir and Phoenix
Episode
60 min
Read time
2 min
Topics
Productivity, Remote Work, Software Development
AI-Generated Summary
Key Takeaways
- ✓Pattern Matching Functions: Define multiple versions of the same function with different argument patterns instead of using conditional branching. Elixir automatically dispatches to the correct version based on data shape, eliminating if statements and case logic while making code more declarative and maintainable.
- ✓Plug Architecture Benefits: Phoenix uses Plug middleware where each request passes a connection struct through a pipeline of functions. Stack traces remain shallow (nine functions deep versus Rails' deep nesting), making debugging straightforward and revealing minimal framework code between your application logic and the response.
- ✓Built-in Concurrency: Background tasks like sending transactional emails require no external queue infrastructure. Use Task.start_async to background processes immediately without Redis, SQS, or similar tools. Erlang's ETS provides in-memory caching, eliminating memcached dependencies for RSS feed caching and similar use cases.
- ✓Turbolinks for Persistent Player: Achieve single-page application behavior (persistent audio player across page navigation) without rebuilding as a React app. Add data-turbolinks-permanent attribute to player div and data-turbolinks-off to admin links. Solves specific SPA needs without full architectural changes or JavaScript framework overhead.
- ✓Production Learning Path: Build functional Phoenix applications without understanding GenServers, supervision trees, or advanced Erlang concepts. Focus on web development patterns first—Ecto queries, controllers, templates. The underlying concurrency power exists when needed, but pragmatic web apps succeed using surface-level features and standard Postgres databases.
What It Covers
Jerod Santo explains how Changelog rebuilt their podcast platform using Elixir and Phoenix after outgrowing WordPress, covering pattern matching, functional programming concepts, deployment strategies, and why they chose Elixir over continuing with Ruby on Rails.
Key Questions Answered
- •Pattern Matching Functions: Define multiple versions of the same function with different argument patterns instead of using conditional branching. Elixir automatically dispatches to the correct version based on data shape, eliminating if statements and case logic while making code more declarative and maintainable.
- •Plug Architecture Benefits: Phoenix uses Plug middleware where each request passes a connection struct through a pipeline of functions. Stack traces remain shallow (nine functions deep versus Rails' deep nesting), making debugging straightforward and revealing minimal framework code between your application logic and the response.
- •Built-in Concurrency: Background tasks like sending transactional emails require no external queue infrastructure. Use Task.start_async to background processes immediately without Redis, SQS, or similar tools. Erlang's ETS provides in-memory caching, eliminating memcached dependencies for RSS feed caching and similar use cases.
- •Turbolinks for Persistent Player: Achieve single-page application behavior (persistent audio player across page navigation) without rebuilding as a React app. Add data-turbolinks-permanent attribute to player div and data-turbolinks-off to admin links. Solves specific SPA needs without full architectural changes or JavaScript framework overhead.
- •Production Learning Path: Build functional Phoenix applications without understanding GenServers, supervision trees, or advanced Erlang concepts. Focus on web development patterns first—Ecto queries, controllers, templates. The underlying concurrency power exists when needed, but pragmatic web apps succeed using surface-level features and standard Postgres databases.
Notable Moment
Santo discovered Elixir's approachability when he built a Slack invite web app in two to three hours as his first Phoenix project. That quick win provided enough momentum to commit to rebuilding the entire Changelog platform, proving the framework's productivity despite functional programming's learning curve.
You just read a 3-minute summary of a 57-minute episode.
Get Full Stack Radio summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from Full Stack Radio
153: DHH – Omarchy and Designing Your Own OS on Arch Linux
Aug 21 · 76 min
Decoder
Yahoo CEO Jim Lanzone on reviving the web's homepage
Mar 16
More from Full Stack Radio
152: Ben Orenstein - How to Stand Out When Applying for a Job at a Small Company
Jan 28 · 47 min
Masters of Scale
How to balance a two-sided marketplace, with Care.com CEO Brad Wilson
Jun 25
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
“Jerod Santo explains how Changelog rebuilt their podcast platform using Elixir and Phoenix after outgrowing WordPress, covering pattern matching, functional programming concepts, deployment strategies, and why they chose Elixir over continuing with Ruby on Rails.”
“Phoenix uses Plug middleware where each request passes a connection struct through a pipeline of functions. Stack traces remain shallow (nine functions deep versus Rails' deep nesting), making debugging straightforward and revealing minimal framework code between your application logic and the response.”
“Jerod Santo explains how Changelog rebuilt their podcast platform using Elixir and Phoenix after outgrowing WordPress, covering pattern matching, functional programming concepts, deployment strategies, and why they chose Elixir over continuing with Ruby on Rails.”
“Background tasks like sending transactional emails require no external queue infrastructure. Use Task.start_async to background processes immediately without Redis, SQS, or similar tools.”
“Erlang's ETS provides in-memory caching, eliminating memcached dependencies for RSS feed caching and similar use cases.”
“Achieve single-page application behavior (persistent audio player across page navigation) without rebuilding as a React app.”
“Background tasks like sending transactional emails require no external queue infrastructure. Use Task.start_async to background processes immediately without Redis, SQS, or similar tools.”
- TurbolinksRecommended
“Achieve single-page application behavior (persistent audio player across page navigation) without rebuilding as a React app. Add data-turbolinks-permanent attribute to player div and data-turbolinks-off to admin links. Solves specific SPA needs without full architectural changes or JavaScript framework overhead.”
company
“Sponsors: Cloudinary, cloudinary.com”
“Sponsors: DigitalOcean, do.co/fullstack”
More from Full Stack Radio
We summarize every new episode. Want them in your inbox?
153: DHH – Omarchy and Designing Your Own OS on Arch Linux
152: Ben Orenstein - How to Stand Out When Applying for a Job at a Small Company
151: DHH – Building HEY with Hotwire
150: Secret Screencasting Tips & Behind the Scenes of Tailwind CSS 2.0
149: Choosing a Payment Processor, Radical Icons & W3C Hype
Similar Episodes
Related episodes from other podcasts
Decoder
Mar 16
Yahoo CEO Jim Lanzone on reviving the web's homepage
Masters of Scale
Jun 25
How to balance a two-sided marketplace, with Care.com CEO Brad Wilson
In Good Company with Nicolai Tangen
Jun 19
HIGHLIGHTS: Sridhar Ramaswamy - CEO of Snowflake
In Good Company with Nicolai Tangen
Jun 17
Snowflake CEO: Scaling Data, AI Agents and the New Software Era
The TWIML AI Podcast
Jun 16
Why AI Agents Break the GenAI Security Model with Devvret Rishi - #770
Explore Related Topics
This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into Full Stack Radio.
Every Monday, we deliver AI summaries of the latest episodes from Full Stack Radio and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime