Felix Sargent - How to deal with “code smell” ie technical debt

Highlights of my conversation with Felix:

• Technical debt is a warning sign
• Liability in the code is not the same as technical debt
• Dealing with “code smell”
• Trying to quantify technical debt
• You need cause to dive into technical debt
• Very important to set your standards
• Define when things are “done”
• Why are you digging into the code?
• What things are and what they should be

Meet: Felix Sargent is a Sr Software Engineering Manager at Truework. He has years of experience working on high-throughput platforms at scale. He’s been part of the larger tech community since 2008, and has driven industry-wide conversations around flexible product management, API design, managing technical debt, and building engineering teams. He believes teams work best when they feel safe, and are well equipped for their challenging work.

His specialties are backend product and engineering management, developer tools, cloud infrastructure, containers, and deployment pipelines. He’s great at taking existing platforms and scaling them up to be more reliable, secure, and performant. He loves digging into obscure business logic and simplifying workflows.

If you have any questions for Felix, please feel free to reach out via:

https://www.linkedin.com/in/felixsargent/

I hope you enjoyed the episode. The best place to connect with me is on Linkedin - https://www.linkedin.com/in/amirbormand (Amir Bormand). Please send me a message if you want me to cover specific topics with future guests.