Table of Contents
Probably each person that was ever involved in software development is familiar with the term Technical Debt. It is a brilliant metaphor that was brought from the financial world and that represents the behaviour of code maintenance and scalability over time. I would like to talk today about software debt; functional debt & technical debt.
Whenever you are forced to leave some parts of your code with a ‘To Do’, ‘Refactor’, or ‘Review Later’ mark, it’s an additional piece of debt you acquire. This way you get some Cash, to buy some Time. You meet the deadline, you launch the product on time and you have a prototype to show for an investment round. But you can’t forget about the cutbacks made in code quality, because it’s your debt. It’s something you owe, it’s something you need to pay back.
If you ignore it and continue to build up on it, your product will progressively become less stable and less scalable and it’s maintenance cost will skyrocket. To keep the analogy with the real world, it’s like taking a new loan to pay back the one you took earlier, repeatedly.
At first, things seem to work fine. But as the loan grows to cover the interests and other expenses, it’s like a rolling snowball that you just can’t stop. This is why it is important to allocate the needed time to refactor and even sometimes to rebuild the marked parts of code.
Even though we are very familiar with this situation, we’ve found a workaround to achieve both the Time (deliver on time) and avoid the Technical Debt. But as a result, in the very end, we get a new form of debt. Something I like to call Functional Debt.
I did a small research for this idea and I found just a few references of this phenomenon, and to be honest, it was never the way I personally see it. In this article by Mark Barnes, it is described as the unfulfillment of YAGNI principle. When we choose a very heavy and powerful framework for what should be a ‘lightweight’ and small project. When the functionality we offer overpasses the functionality we need, the development and maintenance of those extras becomes a Functional Debt.
When I picture a Functional Debt, it’s not exactly what I think about. The way I see it is that in order to deliver it on time, the functionality is implemented partially. The functionality itself suffers from cutbacks. Let’s say that we need to deliver a simple form with a few fields and file input. As we are tight on time and that we don’t want to introduce a Technical Dept, we decide to ‘simplify’ the functionality. We eliminate the ‘drag & drop’ for the file attachment, support for multiple files, and the fields’ verifications’ on legitimacy of the introduced data.
Our application works perfectly fine, code is clean (the parts that are present don’t need to be modified), and we deliver it on time. It is a miracle. Well, it’s not. By doing this, we keep invalid data in our database and the user experience is not good enough. Our code is spotless, and does exactly what we expect. We don’t have Technical Debt. Our debt is Functional.
Later on, we will have to come back to this form, and add new parts, integrate a validation service, and change the UI. As time passes by, all developers will not recall exactly what is missing. They will need time to study what has to be done, and they will need to deal with the toxic data that we allowed in our database. The time invested here is much higher than the time needed to have the full functionality done in the first place. It’s the fee we pay, the pay off of our dept. It’s effects are less harmful than the Technical Debt’s effects, yet are still needed to be watched and taken care off.
The developer that exposes situations like the one described above is often seen as the enemy of productivity as he asks for time to work on something that is already working. It is beneficial to stop for a moment and think about the possible Functional Debt we might be taking, as it might save us a headache or two.
If you need any help with functional or technical debt, count on us, we are experts in software development.