Working Code Podcast - Episode 60: Technical Debt
Every software application has "technical debt". Some of that debt is acquired through meaningful consideration: short-term value gained in lieu of longer-term ease-of-maintenance. And, some of that debt is obtained incidentally through a lack of experience and a dearth of business knowledge. This week, the crew discusses technical debt in their web applications. And goes so far as to say that taking on technical debt is a necessary negotiation within every successful product development life-cycle.
All that and more on this week's show:
... featuring these beautiful, beautiful people:
- Adam Tuttle → Website, Twitter, LinkedIn
- Carol Weiler → Twitter, LinkedIn
- Tim Cunningham → Twitter, LinkedIn
- Ben Nadel (that's me) → Website, Twitter, LinkedIn
With audio editing and engineering by ZCross Media.
For the full show notes and links, visit the episode page. And, be sure to follow the show and come chat with us on Discord! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. New episodes drop weekly on Wednesday.
I would go so far as to say that if you're not taking on technical debt, then you're doing it wrong. To not have technical debt means that you are focusing more on perfection and less on delivering value to your users / customers. Consider reading my other post on the related issues:
Post A Comment — ❤️ I'd Love To Hear From You! ❤️
❤️ ❤️ Thank You For Your Comment ❤️ ❤️
In order to keep this website fun, safe, and full of those sweet, sweet feelings, your comment has been submitted for approval.