3 ms·
> Instead of taking weeks or months to develop a custom application, it can be done in a few hours or days. In other words, "pile up massive amounts of technic
by metalliqaz 7y ago
> Instead of taking weeks or months to develop a custom application, it can be done in a few hours or days.
In other words, "pile up massive amounts of technical debt"
- coffee 7y agoThat's a bit snarky. I've been engineering software for a long time and I've never come across a code base (associated with a successful product) that was debt free.
- metalliqaz 7y agoPerhaps a bit snarky, but sincerely spoken. This concept reminds me quite a bit of the "applications" I've seen floating around in big companies. They are creations of convenience, based on MS Office documents because there weren't any real programmers around. They may have been initially fine, but grow and grow until they are completely unwieldy. By that time they are critical path and mission critical, and nobody can handle the complexity.
- elsurudo 7y agoThen that is a failure of management – that they didn't make the proper investments when the time came. It doesn't necessarily mean that taking on that debt early on didn't make sense.
- jdjsjsbshb 7y agoI mean, so what though? I feel like we complain about technical debt often without acknowledging that the point of taking on debt, traditionally, is to capture potential growth. Sure it'll be a hassle to be the guy who has to handle the eventual revamp, but that's just a reason for that guy to ask for more money. At the point of turning a week into hours you're playing a totally different game than you were before.
- JohnFen 7y ago> that's just a reason for that guy to ask for more money. It sounds like you're arguing that technical debt is no big deal because you can leave for greener pastures before the bill for that debt comes due. Am I misunderstanding you here?