Re:Can't Be Fucked: Underrated Cause of Tech Debt
by belval on Thursday October 12, 2023 @01:58PM
(#37860606)
Personally these can be the best bugs though because you have an opportunity to learn something new (your work environment is everything though). Compare that to a ticket in an older codebase with hard multi-cause bugs that are just painful to debug and leave you with nothing but a deeper understanding of something that is slipping into irrelevance by the day.
Re:Can't Be Fucked: Underrated Cause of Tech Debt
by Terr_ on Thursday October 12, 2023 @02:11PM
(#37860754)
"I found the bug, but it's because the business process you want to model is fundamentally insane and you're asking the computer to do magic."
Re:Can't Be Fucked: Underrated Cause of Tech Debt
by belval on Thursday October 12, 2023 @03:08PM
(#37861642)
In my experience, administrative process that was previously done by a bunch of administrative assistants and then "computerized" around the year 2000.
The original stakeholders are long gone, the system is too valuable to be replaced and each quirk handles specific cases that are not documented anywhere. Bonus point if it's in a semi-dead language like VBScript. Please fix.
Re:Can't Be Fucked: Underrated Cause of Tech Debt
by verve_rat on Thursday October 12, 2023 @04:23PM
(#37862713)
I'm going to frame this and put it on my wall.
Re:Can't Be Fucked: Underrated Cause of Tech Debt
by actionfromafar on Thursday October 12, 2023 @02:45PM
(#37861241)
How did your character change?
Re:Can't Be Fucked: Underrated Cause of Tech Debt
by Terr_ on Thursday October 12, 2023 @04:02PM
(#37862425)
One evil-twin goatee, one villainous laugh.
Re:Can't Be Fucked: Underrated Cause of Tech Debt
by DanielHB on Friday October 13, 2023 @03:38AM
(#37867870)
I once ran into a bug that only happened in a specific version of the linux kernel when combined with a specific version of the java JDK, worse 2-3 weeks of troubleshooting of my life.
We found an issue in the kernel bug tracking that seems to explain it, but we never confirmed for sure. Fortunately updating either of those things fixed the issue. This was of course also hard because this was back in the golden days of vmware managed by client's IT team, so getting them to update things on a VM was hell as well.
That with zero C/C++ experience, being asked to figure out why the newer version of the Linux kernel is randomly crash-panicking after getting cross-compiled for a custom hardware box. ("He's familiar with the the build system, so...")