/https%3A%2F%2Fmedia24.fireside.fm%2Ffile%2Ffireside-images-2024%2Fpodcasts%2Fimages%2Fc%2Fcf46278b-b0e2-4c19-bb2d-a4220cbf6aab%2Fcover.jpg%3Fv%3D2)
The Friday Deploy
John Nunemaker
Episode 1: Changing the Wheels While the Car Is Moving
SEP 25, 202655 MIN
/https%3A%2F%2Fassets.fireside.fm%2Ffile%2Ffireside-images-2024%2Fpodcasts%2Fimages%2Fc%2Fcf46278b-b0e2-4c19-bb2d-a4220cbf6aab%2Fepisodes%2Fe%2Fe0839f74-3d30-43d4-b914-6d1492c48ead%2Fcover.jpg%3Fv%3D1)
Description
When John, Garrett and Kris bought Fireside, they inherited an eight-year-old Rails app running on Ruby 2.7, Rails 5, Postgres 9.5, and aging infrastructure that could not simply be switched off and rebuilt.
Two years later, almost every piece has been replaced while podcasts, feeds, and downloads kept running.
In the first episode of The Friday Deploy, they break down how they rebuilt Fireside while it was live, including a jump from Postgres 9.5 to 18 with no downtime for listeners. They talk about reverse-engineering undocumented infrastructure, using Flipper to put the application into read-only mode, testing migrations until they became boring, and letting agents carry work all the way to the final approval.
This is not a story about giving an AI agent one prompt and letting it loose on production. It is about breaking dangerous work into small, verifiable steps and knowing where experience and taste still matter.
They also get into:
Why verification matters more than another round of prompting
How multiple models can provide independent reviews
Giving agents safe, read-only access to production context
Keeping deterministic work out of nondeterministic agents
Using real customer data to guide product and interface decisions
Scheduled tasks as the beating heart of an AI-assisted workflow
Whether the next generation of software needs a traditional interface at all
The goal is not to eliminate risk. It is to gather enough evidence that shipping stops feeling like a leap of faith.
Links:
Fireside
Flipper
Flare

