About this episode
On this week's episode, Steph & Chris take a deep dive into all things technical debt. How do you know when your code has reached "good enough"? When might we purposefully knowingly take on technical debt? How do we tackle existing technical debt without halting new development? How can we tell high-interest, hair on fire debt from "ehh, it's fine" debt that we can let lie? Tune in to find out!
This episode is brought to you by:
- ScoutAPM - Give Scout a try for free today and Scout will donate $5 to the open source project of your choice when you deploy
- FusionAuth - Use it for free today and get a free t-shirt, or upgrade to their paid editions and get 25% with promo code
BIKESHED
- Rack::Timeout Sigterm
- The Art of Code Comments - Sarah Drasner | JSConf Hawaii 2020
- Technical Debt Panel from thoughtbot
- Gary Bernhardt on Full Stack Radio
- Sandy Metz - The Halflife of Code
- Code Climate Churn vs Complexity Graph
Become a Sponsor of The Bike Shed!
Get every episode summarized
Each time The Bike Shed publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
