Re:Technical debt as an opportunity to accumulate technical ...
by hinkley on Monday August 15, 2016 @11:29PM
(#12295352)
I heard a phrase a couple months ago that I believe sums this up. What you want is local reasoning. You need to be able to estimate the scope of consequences of a change so you can act accordingly. You also need to be able to look at a problem and estimate the scope of code that could be causing the problem.
We have a bunch of rules and guidelines that work toward that goal but if you don't know the destination you may never arrive.
We have a bunch of rules and guidelines that work toward that goal but if you don't know the destination you may never arrive.