3 ms·
Not all code debt contains massive downsides. The key to using technical debt wisely is understanding the difference, and architecting a system that is loosely
by grandalf 12y ago
Not all code debt contains massive downsides. The key to using technical debt wisely is understanding the difference, and architecting a system that is loosely coupled to allow strategic debt to be taken on in places where it makes sense.
- pm 12y agoTechnical debt is an elegant analogy. However, I find the majority of systems on which I work are not loosely coupled. And yet, judging from the notes left by my antecedents, "loosely coupled" was the ideal for which they were striving. Is there a metric, or at least a heuristic, that can be applied in this situation?
- grandalf 12y agoI think the key is for developers to understand coupling. There are lots of kinds of coupling. This book, is not specifically about coupling but the first chapter is an excellent overview that all developers should read: http://www.apress.com/9781590596432/ http://www.apress.com/9781590596432/