Technical debt is an elegant analogy. However, I find the majority of systems on... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		pm on Dec 21, 2014 \| parent \| context \| favorite \| on: Bad code isn’t technical debt, it’s an unhedged ca... Technical 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 on Dec 22, 2014 [–]

I 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/

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact