3 ms·
Is someone who takes a financial loan procrastinating paying their bills? Or are they solving a short term problem the best way they know how? Procrastination
by chatmasta 11y ago
Is someone who takes a financial loan procrastinating paying their bills? Or are they solving a short term problem the best way they know how?
Procrastination may lead to technical debt, but it's not the only source. The biggest source of technical debt is insufficient planning for future product requirements, leading to old code blocking new features.
That's why the concept is called "debt," because it's as if you took out a loan on the first iteration of the product, and then many features later, you're still paying interest on that loan.
So no, technical debt is not purely the result of procrastination. Sure, procrastination, especially in the planning stage, can create technical debt. But even the most productive people, those mythical creatures who never procrastinate, are vulnerable to creating technical debt for themselves. In fact you might argue they're more likely to create technical debt, if they choose to skip the planning phase and jump right into coding.
- nlawalker 11y ago>> insufficient planning for future product requirements This covers both low prioritization and procrastination, the former of which I think is what you're getting at, and the latter of which I think is what purpled_haze is talking about. It's the difference between "we'd like to clean up this technical debt but these new features are too pressing" and "we have nothing else going on, we're going to clean up this technical debt..." and then never doing it. In my experience, the latter happens because no one ever generates a real execution plan to get it done, often because there's just no reward for doing so.
- bpchaps 11y agoI don't know if "debt" or "procrastination" are really the correct words. It seems to be somewhat in the middle of the two, where the problem comes from "We'll take care of that in the future." where the future never comes. A good example of that might be in log refactoring. I recently quit a place for what amounted to a complete lack of interest in correcting bad logs. After spending 8 hours trying to fix some non-prod issues and being completely halted by timeout errors, I was told "Those errors are fine, they even happen in prod (!!!). We talked about fixing it, but agreed to do it way further down the line." So, not really procrastination or technical debt, but something similar since it's 'debt' and 'procrastination' are simply symptoms of a larger problem.