138
How to explain Technical Debt to your Boss
(feddit.org)
Hey Boss, look here!
I made a magical X-ray app that displays our code as wiring.
Here is the shiny, neat program that Bob wrote 15 years ago, right before he left us:
And here is what it is today, after Tom took it from Bob, and Jane from Tom, and Mick from Jane, and me from him, porting it to roughly four new platforms, and adding about 240 features from customer requests (150 of which were urgent):
That’s because this is a broadcast rack (probably for sports) sending SDI over all those cables, notice it’s all BNC not Ethernet. This is probably in a truck that needs to get packed up and shipped to the next game/race/whatever and so doing it all in Velcro with service loops is asking for shit to fall apart on the road for you to find with like a 24 hour timeline until the event
So that’s why shits locked down, it ain’t web server shit
Point still stands, OP is making a poor comparison.
Might be a poor comparison, but that doesn't mean it's necessarily a bad way to present it to thier boss. If the analogy, however flawed, communicates the underlying idea to the listener, then it was effective.
The concept here is very related to why "ceci n'est pas un pipe" is/was compelling.