2 ms·
IMHO there are parallels with "physical" engineering if you look carefully. Here are some examples: 1) We figure out that asbestos is bad, mmkay. Now suddenly
by PeterisP 7y ago
IMHO there are parallels with "physical" engineering if you look carefully. Here are some examples:
1) We figure out that asbestos is bad, mmkay. Now suddenly half of the buildings have a need to perform expensive maintenance work even though their business needs for "features" have not changed - that's analogous to finding a security vulnerability in a subsystem or protocol that's not even your own but that your system uses, where fixing that may take a lot of work.
2) For electric wiring. You may have a building wired properly according to code requirements as it was in 1950. Nowadays we have a better understanding of what's safe and not, and while you're often not required to fix that immediately, in many places you wouldn't be allowed to "just" do minor changes - if you do alterations, then after you're done that place must be meet the current code requirements, which may require extensive expensive work. This has a clear analogy to the type of technical debt caused by relying on an obsolete version of some dependency - adding small new stuff may force you to do integration work so that your system works with a newer version of that dependency.
3) Another example of electric wiring - you may sometimes encounter improper work done that way to save time or money because of some urgent deadline. And you can't just come in and make up the missing parts later - fixing it often requires simply ripping all of it out and putting in the wires properly; so if it's not a temporary place that's up for demolishing soon (just as with software, temporary structures also sometimes stay used much, much longer than planned) then you need to re-do it eventually if you want to keep using it safely. And there are cases just like that in software.
People handling construction and reconstruction projects, as well as all their customers, have some understanding of these concepts when it applies to the physical world, and it's not that surprising to them (well, the costs for the tasks mentioned above are sometimes unpleasantly surprising) - so perhaps we should frame it in similar terminology to piggyback off of these analogies instead of debt?
- alacombe 7y agoOr the company can't source the same materials / quality as before (supplier change, company moves, etc) and need to go into trouble fulfilling existing orders with the old design (paying extra both time and money for the old material) while trying to sort out a new design with the new material available...
- PeterisP 7y agoYes, companies sometimes have to redesign their product (costing a bunch of time and money and potentially making it worse) because they can't supply some ingredient or technical part anymore and have to use something else... which is pretty much the same thing as having to rework your system because a software dependency you're using isn't supported anymore. Furthermore, you may simply be working with a supplier where you know that they're stopping production or going out of business soon, and you know that you'll need to rework your physical product soon but haven't started doing that yet, such cases happen, they'd show up on internal risk assessments and shareholder reports - and I'm not certain how this class of challenges as a whole would be called in the (non-software) business world, but it's definitely not "debt".