How to manage technical debt with Lou Franco

https://is1-ssl.mzstatic.com/image/thumb/Podcasts211/v4/cc/17/b2/cc17b28e-dc17-28a5-ba96-b5a99bc92f41/mza_6646550504722810147.jpg/600x600bb.jpg

Coding Chats

John Crickett

54 episodes

2 days ago

On Coding Chats, John Crickett interviews software engineers of all levels from junior to CTO. He encourages the guests to share the stories of the challenges they have faced in their role and the strategies and tactics they have used to overcome those challenges providing actionable insights other software engineers can use to accelerate their careers.

Technology

RSS

All content for Coding Chats is the property of John Crickett and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

Technology

https://d3t3ozftmdmh3i.cloudfront.net/staging/podcast_uploaded_nologo/40748596/40748596-1710690984838-6b00cf26b3b39.jpg

How to manage technical debt with Lou Franco

Coding Chats

56 minutes 16 seconds

2 weeks ago

How to manage technical debt with Lou Franco

Coding Chats episode 50 - Lou Franco discusses the concept of technical debt, its implications for software development, and the importance of quantifying it. He emphasizes that technical debt is not just a financial metaphor but a real issue affecting developer productivity and team dynamics. The discussion also covers the role of managers in understanding and addressing technical debt, the importance of metrics, and the eight questions that can help teams evaluate their technical debt. Additionally, the conversation touches on the impact of AI on technical debt management, highlighting both its potential benefits and challenges.

Chapters

00:00 Understanding Technical Debt

03:17 The Financial Metaphor of Tech Debt

06:04 Defining Technical Debt: Internal vs External Effects08:59 The Role of Developer Productivity

12:05 The Team Responsibility of Technical Debt

14:51 Why Managers Should Care About Tech Debt

18:05 Quantifying Technical Debt for Visibility

20:57 Improving Developer Productivity

23:43 Communicating Tech Debt to Executives

26:41 Understanding Technical Debt and Its Management

36:37 The Eight Questions for Managing Technical Debt

46:29 AI's Role in Technical Debt: A Double-Edged Sword

Lou's Links:

LinkedIn: https://www.linkedin.com/in/loufranco/Book: https://loufranco.com/tech-debt-book

John's Links:

John's LinkedIn: https://www.linkedin.com/in/johncrickett/

John’s YouTube: https://www.youtube.com/@johncrickett

John's Twitter: https://x.com/johncrickett

John's Bluesky: https://bsky.app/profile/johncrickett.bsky.social

Check out John's software engineering related newsletters:

Coding Challenges: https://codingchallenges.substack.com/ which shares real-world project ideas that you can use to level up your coding skills.

Developing Skills: https://read.developingskills.fyi/ covering everything from system design to soft skills, helping them progress their career from junior to staff+ or for those that want onto a management track.

Takeaways

Technical debt is often misunderstood and miscommunicated.

The financial metaphor of technical debt can be misleading.

Technical debt can arise from changing technologies, not just poor choices.

Developers experience anxiety due to technical debt affecting estimates.

Managers need to understand the visible effects of technical debt.

Quantifying technical debt helps in communicating its impact.

The eight questions framework aids in evaluating technical debt.

AI can assist in managing technical debt but requires careful oversight.

Collaboration with other teams can provide valuable insights into technical debt.

Technical debt should be viewed as a team responsibility, not just an individual issue.