5 ms·
As far as I can tell, this article is saying "if you define technical debt as something that isn't too bad, technical debt isn't too bad". The article draws a
by michaelt 13y ago
As far as I can tell, this article is saying "if you define technical debt as something that isn't too bad, technical debt isn't too bad".
The article draws a distinction between bad code and technical debt - that things that make it hard to refactor a system are not 'technical debt' but 'bad code'. It's my experience that being unable to refactor systems is a consequence of accumulated technical debt - that as the interest compounds, bad designs build on top of bad designs and you can't fix the first bad design because the second bad design relies on it.
And the more expensive it gets to pay down the technical debt, the less anyone wants to pay to do it.
- atrk 13y agoMy experience is just the opposite - systems being hard to adapt to changing models of reality is usually a bigger function of "bad code." If I can understand the code, I can tell that it's "wrong" i.e. that it doesn't match my model of reality. If I can't understand the code, I can't tell whether it's right or wrong, which makes me afraid to change it in case I'm making it wrong-er.
- michaelt 13y agoWell, you can have code that is a fantastic high quality implementation of a flawed architecture. For example: Backend team: As we are building an MVP, this database table will have a poorly designed schema we will iterate on later. Frontend team: We need some data that only exists in that other team's database. We will accumulate some technical debt by reading their database directly. This will let us deliver working software quickly. Backend team: The time has come to refactor that badly designed schema. Frontend team: That will break everything. You must not do it. Backend team: Please will you pay off that technical debt? Frontend team: It's not hurting us much at all, and we would rather be working on new features and things that make money. We are busy and many people are asking us for important things. Here is a link to an article saying technical debt is not a bad thing. Backend team: I am sad because I'm stuck looking after this badly designed table. I wish I had done a big design up front.
- chazu 13y agoThe lack of contractions in the above exchange really puts it over the top for me.
- deleted 13y ago[deleted]
- taeric 13y agoThis does seem to be an odd distinction. Though, I think the metaphor of technical debt does support the interpretation. At least to a degree. Technical debt should be viewed the same as any debt. With a major caveat being that there is no time limit on it. And to that end, you don't always have to pay down your debt. The problem, I think, is everyone applies personal financing to thinking of technical debt. Very rarely can an individual accrue debt that will allow them to make money. It is not at all uncommon to make a design trade off that "pays dividends" pretty much immediately. And, not too shockingly, xkcd has a good visualization on this. http://xkcd.com/1205/ http://xkcd.com/1205/ (Granted, I can see how this is not necessarily the same thing. But I often feel that what folks call "technical debt" is really, "I wanted a jet liner solution for what a walk down the street could have accomplished.")
- Retric 13y agoI agree with what your saying, but the important idea with Technical debt is it's the interest rate and payments that you really need to consider not the capital. A lot of terrible UI code may be acceptable as it rarely infects the rest of the system where a smaller design bug in a tiny utility library may end up causing worlds of pain even if it's rather elegant code that could be reused on other projects just fine.
- taeric 13y agoApologies for a rather late response on this one. I think the "technical debt" view of this would more be that it makes sense to rely heavily on some third party libraries and frameworks to organize and execute your UI. You are taking out a debt against their knowledge in getting your application off the ground. This directly so if it has to be licensed, but equally true for free frameworks. My argument is that for many people this will never be a problem. Consider how many games farm out the heavy graphics coding to libraries. For many software companies and content producers, the content that you are producing is the value they bring. Trying to morph the actual value of a company into a new way of doing this is risky. Which brings me to a comment I made in another subthread. The one thing people need to remember is that when you take out technical debt by using a framework or library, you are basically entering a contract to do things their way. Take great care when you break this contract.
- pm 13y agoI've also seen technical debt accumulate when teams choose to build upon an "MVP" when the MVP was in fact just a prototype. Not nearly enough code is thrown away at the start of projects.
- dllthomas 13y ago"Write it, throw it away, rewrite it."
- deleted 13y ago[deleted]