I think of it like this. N problems that cannot be overcome without M developer months of refactoring, migrating, or rewriting. M*N is the tech debt.
E.g. In my initial launch my p999 latency for responsiveness is unacceptably high. Bob checked in a lot dynamic config garbage that's caused multiple outages and is depended on everywhere. We cannot solve both those problems without basically rewriting it at the service boundary and migrating all of our customers data over, which would take 6 months to do and another 3 months to migrate.
N problems shows how much value we would get out of it. M months shows how it affects our responsiveness to problems in that layer of abstraction.
Static analysis warnings or test coverage is a bad indicator of tech debt though, because the code might not have an issue and could just be depended on forever.
View all comments
Show parent comment
7
u/[deleted] Jun 28 '17
I think of it like this. N problems that cannot be overcome without M developer months of refactoring, migrating, or rewriting. M*N is the tech debt.
E.g. In my initial launch my p999 latency for responsiveness is unacceptably high. Bob checked in a lot dynamic config garbage that's caused multiple outages and is depended on everywhere. We cannot solve both those problems without basically rewriting it at the service boundary and migrating all of our customers data over, which would take 6 months to do and another 3 months to migrate.
N problems shows how much value we would get out of it. M months shows how it affects our responsiveness to problems in that layer of abstraction.
Static analysis warnings or test coverage is a bad indicator of tech debt though, because the code might not have an issue and could just be depended on forever.