I’m always curious about how we think about “tech debt” and “throw away work” because it’s all code on a timeline...throw away work is code that didn’t make it or live in production long enough and technical debt (sometimes) is code that has lasted too long.
Good summary. I'd like to add that consistency is key to keep the tech debt under control.
I've recently writte about how one team did it on a biweekly basis and what were the results. Not exactly a scientific paper but goes to show that what the authors call "balanced" approach actually works.
I’m always curious about how we think about “tech debt” and “throw away work” because it’s all code on a timeline...throw away work is code that didn’t make it or live in production long enough and technical debt (sometimes) is code that has lasted too long.
Good summary. I'd like to add that consistency is key to keep the tech debt under control.
I've recently writte about how one team did it on a biweekly basis and what were the results. Not exactly a scientific paper but goes to show that what the authors call "balanced" approach actually works.
Link: https://blog.alexewerlof.com/p/tech-debt-day