Navigating Technical Debt and Code Quality in Agile Teams
from How Many CTOs Hosted by How Many CTOs Podcast
In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss a recent incident in a small engineering team that highlights challenges of managing technical debt even with skilled developers and robust code review processes. They explore the importance of refactoring in agile methodologies, the pitfalls of large pull requests, and the complexities of quantifying and prioritizing technical debt. The conversation touches on the limitations of traditional code review processes and the potential of automated CI tools to enforce code quality. The episode underscores how even well-intentioned teams can fall prey to subtle coding anti-patterns and offers insights for improving tech debt management at different organizational scales. 00:00 Introduction and Welcome 00:30 Discussing a Recent Incident 00:58 Importance of Code Reviews 03:00 Challenges in Code Refactoring 05:25 Code Review Process and Human Error 07:22 Tools and Strategies for Code Quality 08:11 Evaluating and Managing Tech Debt 15:47 Conclusion and Call to Action 16:06 Outro and Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/ Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/ Defining, Measuring, and Managing Technical Debt - Google Research https://ieeexplore.ieee.org/document/10109339 #podcast #technology #leadership #ctos #technicaldebt #management #leadership #problemsolvingtechniques #problemsolvingstrategies #engineering #entrepreneurship #engineeringmanagement #codereviews #cicd
Embed this episode
No transcript yet.