# Three ways to plan an upgrade when your codebase is a patchwork Page: https://stenobird.com/podcast/no-compromises-1309932/three-ways-to-plan-an-upgrade-when-your-codebase-is-a-patchwork Text version: https://stenobird.com/podcast/no-compromises-1309932/three-ways-to-plan-an-upgrade-when-your-codebase-is-a-patchwork.md Podcast: [No Compromises](https://stenobird.com/podcast/no-compromises-1309932) Published: 2026-02-14T06:00:00+00:00 Episode link: https://share.transistor.fm/s/912b7642 Audio file: https://media.transistor.fm/912b7642/7d98fdcc.mp3 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/three-ways-to-plan-an-upgrade-when-your-codebase-is-a-patchwork Duration seconds: 599 ## Resource When your project has the same thing done three different ways, how do you bring everything up to date with a consistent approach? In the latest episode of the No Compromises podcast, we discuss different strategies for tackling upgrades when parts of your codebase are multiple versions behind. We walk through two main approaches and weigh the tradeoffs for both the developer doing the work and the person reviewing it. (00:00) - Setting up the upgrade scenario (02:15) - Approach one: upgrade each area to current (04:00) - Why the reviewer's experience matters too (07:30) - A third approach neither one expected (09:00) - Silly bit Want help upgrading your Laravel project? ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/no-compromises-1309932/episodes/three-ways-to-plan-an-upgrade-when-your-codebase-is-a-patchwork/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/no-compromises-1309932/three-ways-to-plan-an-upgrade-when-your-codebase-is-a-patchwork.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.