Why Software Teams Are Killing Legacy Code

Failed to add items

Sorry, we are unable to add the item because your shopping basket is already at capacity.

Add to cart failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Follow podcast failed

Unfollow podcast failed

Why Software Teams Are Killing Legacy Code

Listen for free

View show details

In this episode of The Programming Languages Podcast, Lucas and Luna tackle the most uncomfortable truth in modern engineering: why smart teams are deliberately deleting working code. They explore the 'zero-based budgeting' approach to software maintenance, where every feature is re-evaluated annually rather than carried forward by default. Using a specific case study from a mid-sized fintech startup that cut its codebase by forty percent while doubling deployment speed, they break down the metrics that justify deletion. You will learn how to calculate the 'maintenance drag' on your team's velocity, identify which legacy modules are actually revenue drivers versus liability, and implement a structured review process that prevents accidental data loss. This is not about technical debt hygiene; it is about strategic resource allocation for engineering leaders who need to move faster without adding headcount. #SoftwareEngineering #CodeMaintenance #LegacyCode #EngineeringLeadership #TechnicalStrategy #FexingoBusiness #BusinessPodcast #TechManagement #DeveloperProductivity #ZeroBasedBudgeting #CodeDeletion #SoftwareArchitecture #TeamVelocity #FintechCaseStudy #EngineeringMetrics #ModernCoding #StartupGrowth #CodeBaseOptimization Keep every episode free: buymeacoffee.com/fexingo

No reviews yet