Anyone familiar with enterprise software development knows about Technical debt. As #nocode enters this world, it's tempting to think that this is not a factor for us. Not true! In fact, I'd argue technical debt is being built up faster in projects using tools like Bubble for both front and backend. The unstructured nature of the platform, ability to build things using multiple different patterns and lack of documentation that usually accompanies this approach, means that code quickly becomes unwieldly, complex, hard to trace and slow to extend. For those new to this concept, here's a primer.. Technical debt refers to the implied cost of additional rework caused by choosing an easy or expedient solution over a better approach that would take longer. It's a metaphor borrowed from the financial concept of debt, where you incur interest by not paying for something right away. In software development, technology debt can accumulate when developers take shortcuts, use quick workarounds, or make compromises to meet short-term goals or deadlines. These shortcut solutions may work initially, but they often create more significant problems down the line, requiring refactoring, rewriting, or rearchitecting the codebase. Managing technology debt is crucial because if left unchecked, it can lead to a codebase that becomes increasingly difficult to maintain, extend, or enhance, ultimately slowing down development velocity and increasing the risk of bugs and system failures. #nocode #enterprisesoftware
Simon Klobas
3mo
Yes, very real and very hard for companies having products built to know what’s actually being done.
Innovating the tech world with low-code at Creme Digital 🍦
3moOutSystems does a lot of of case studies into how bad tech debt is…..and it’s bad haha