Submitted 3 days ago by altkey@lemmy.dbzer0.com to showerthoughts@lemmy.world
It has a long story and a lot of better explanations, but in short
There’s nothing more permanent than a temporary solution
I actually had to realize this because I kept making “good enough” solutions that I told myself I would change later and then never did, until I got so frustrated that it made me stop working on it. Good enough is a big problem if it’s good enough that you never really need to change it.
Supernatural’s whole story arc was based on this (and it worked for them). Inevitably, to beat this big bad that the brothers have absolutely no business going toe-to-toe with, they must do something that is bound to catch up with them, but it’s either that or the world is fucked. Then the next thing is even worse, and they have to do something that will bite them even worse in order to stop the world from getting fucked. And it just keeps ramping up, they keep losing more and more of themselves and punching so far above their weight class that they end up… well, no spoilers, in case somebody wants to watch (and I don’t know how to do spoiler tags).
There’s a point when Sam has some injury, like a broken arm or gunshot wound or something, and he’s talking to a nurse or doctor who asks him to rate his pain from 0, which is no pain, to 10, which is the worst pain he could imagine. He gets a thousand-yard stare for a second and says “3.”
Just a fancier way of saying “quick and dirty”. Couldn’t be bothered to build a proper fix, so I just went with whatever trashy hack that just barely gets the job done.
Quite often (or maybe even most often), but there’s also the realities of simply having to choose a path knowing it will change in 2-5 years.
I’ve seen that first hand. Workers keep complaining how badly the engineers designed some machine. When I talked to the engineer who designed it, he told me it was fine 10 years ago, but many things have changed since then. Nowadays, the machine is sitting in a place where it wasn’t designed to sit and it’s doing things it wasn’t designed to do.
hi-quality shower thought
In a way it’s the plot of Hollow Knight.
Dark Souls as well.
It's not anything close to "debt" though, fucking moronic IT jargon.
It's probably more like maintenance opex that someone doesn't want to bother with. Or an old standard that someone doesn't know how to comply with or doesn't want to because they heard that the new one is "better".
Neglectful asset management and poor maintenance is not going to force anyone into involuntary liquidation. That's always a matter between the borrower and the lender. In the scenario above you have to borrow money at step 1, then suffer a revenue loss at step 3 before the loan was paid off.
I like to call it “debt”, because it’s a problem that grows while you ignore it. Worst case, it becomes easier to start over than fixing it. But getting 100% rid of it isn’t good business either.
Like all other analogies, don’t overthink it. I don’t now what “involuntary liquidation” would mean for tech debt. Unless you mean the product won’t run for a significant amount of time due to overwhelming tech debt, which can absolutely happen.
Yes and with the ‘debt’ analogy one can think of what debt is high interest vs low interest and work on the high interest items first
It’s debt in the sense of obligation, not literal finance. If we get more volume, we’re going to be obligated to change this so it does something smarter than dumping output to a csv on disk. For now it’s fine, even if it’s annoying to scp and parse the files every time you want to see something.
ieatpwns@lemmy.world 3 days ago
Me playing factorio
recentSlinky@lemmy.ca 3 days ago
Me playing Satisfactory
altkey@lemmy.dbzer0.com 3 days ago
I was thinking more about selling a soul to some monkey-paw style demon, but yeah, there I feel seen.
Endymion_Mallorn@kbin.melroy.org 2 days ago
Me playing Mindustry
wesker@lemmy.sdf.org 2 days ago
Me looking at the codebase of my new team.