Three ways to plan an upgrade when your codebase is a patchwork

About this episode

The episode discusses strategies for upgrading a patchwork codebase to ensure consistency across different implementations.

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?

People in this episode

Hosts: Joel Clermont, Aaron Saray

Topics covered

• codebase upgrade
• development strategies
• software consistency
• review process
• Laravel

Keywords

• codebase
• upgrade
• development
• software
• Laravel
• review
• strategies

Mentioned in this episode

Products: Laravel

More episodes of No Compromises

• How much logic is too much logic in a PHP enum · June 6, 2026 · 13 min
• Your codebase is not a museum for old code · May 23, 2026 · 14 min
• Do you actually own the code you ship? · May 9, 2026 · 15 min
• Do you actually need a multi-tenancy package? · April 25, 2026 · 14 min
• Local and production should match even for Laravel tools · April 11, 2026 · 13 min
• When weird code needs to explain itself · March 28, 2026 · 11 min