3 ms·
>writing poor quality code isn’t tech debt. sure it is, in the same way that taking one of those payday loans to cover a coke habit is still real debt, it's ju
by bryanrasmussen 8y ago
>writing poor quality code isn’t tech debt.
sure it is, in the same way that taking one of those payday loans to cover a coke habit is still real debt, it's just real bad debt.
- ljm 8y agoI don’t believe we can equate jonesing for a fresh hit to writing well intentioned but ultimately difficult code or the product of inexperience. Besides which, it trivialises the seriousness and the tragedy of addiction. If you think your tech debt is similar to that you are well equipped to quit your job and work elsewhere. An addict does not have such an easy choice, they can’t leave their addiction to someone else and move on. You choose to take the payday loan or hit up a shark, addiction or no. The point where I concur is when you gamble the short term against the future despite all evidence that you will benefit from spending time to save time.
- UnFleshedOne 8y agoThe victim in that metaphor is not an individual coder who can go work elsewhere, it is the org who takes on technical debt and sometimes can't function at all without the code in question.
- therealjumbo 8y ago>I don’t believe we can equate jonesing for a fresh hit to writing well intentioned but ultimately difficult code or the product of inexperience. Agreed. The addict might recover. Organizations with poor culture are doomed.
- bryanrasmussen 8y agoall analogies and metaphors are in some ways inexact - indeed the whole concept of technical debt as a thing correlating to real debt is fraught with edge cases that don't exactly line up. Nonetheless if the metaphor has some utility then individual expressions of it such as mine will often have some utility - hence your concurring on a single point while finding other implications problematic.
- vsl 8y ago> I don’t believe we can equate jonesing for a fresh hit to writing well intentioned but ultimately difficult code or the product of inexperience. That's not what "technical dept" is. Choosing a quick solution instead of a proper one that would take more effort is. I've made that conscious more than once myself: to hit a deadline, or because I didn't know if the MVP would even survive long enough to worry about code maintenance.
- boltzmann_brain 8y agoPoor quality code is debatable. What seems like a great architecture and clean design to one, may be regarded as the worst thing on earth by another. Code quality measurement is often very subjective and it's difficult to come up with objective criteria. For example, someone coming from embedded world will be appalled by some OOP designs, ridiculous usage of so called "patterns", etc. And the same thing will be regarded as "clean" and high quality by someone else.