Reducing technical debt with CloudRail
Software developers frequently face a dilemma. Well spec’d, good design and following best practice is what we want, but sometimes done is better than perfect, and we have to ship code and meet deadlines (and budgets). So taking on a little technical debt will a lot of times make a lot of sense.
About technical debt
Technical debt is a metaphor used to describe the price you are paying when choosing quick and easy solutions. Quick and easy solutions, which might have to be refactored or replaced at a later time. The debt is the time you might have to spend later to compensate for saving time now.
Technical debt sounds like a negative thing, but it doesn’t have to be. There’s a lot of value in shipping code fast, and going into technical debt doesn’t necessarily mean compromising on quality, but it might. Will the quick solution require continued work-arounds and fixes is that work considered interest on the debt, and the debt will increase.
I now have debt, so I need to pay it down, right? Yes. Usually you pay down the debt by going back and refactoring the code when time allows it, and replace the quick solution with the better solution you intended to implement, but couldn’t at the time. But there are cases where the interest on the debt is so little, meaning it doesn’t require any significant additional work, and the solution works well in your application. In those cases it might not make sense to pay down the debt. That’s the ideal type of technical debt.
CloudRail interest-free integrations
At CloudRail we strive to create solid, scalable unified API integrations you can quickly implement in your application, without going into deep technology debt. CloudRail allows you to focus on building meaningful features, instead of studying 3rd party API documentation.
By implementing CloudRail’s SDK in your application, you get a solution where you can integrate popular APIs in your application, through a single unified API. This will not only save you development time, you also have less code to test and less code to maintain.
3rd party APIs are not static, they can easily change over time. With CloudRail you don’t have to monitor these changes, we take care of that part, and update the library. In case of changes, you will be notified, and all you need to do is update the library. No code changes are necessary on your end. This reduces the time you spend on maintaining your application, reduces risk of breaking features and reduces testing. That’s why we consider the SDK to be interest-free technology debt.