A while back I was developing a workflow scheduler. However the run duration kept coming back negative. The runs kept finishing like 15 seconds before they started. Eventually I figured out why; the company had configured a policy to use their custom NTP server, but it was 16.7 seconds off. So my Windows laptop’s time was in the future, but the WSL VM (which ran the program) used another NTP server and was correct. In the end I just added a bodge that made the program request the time from an external server on startup to calculate an offset.
I’ve told this story before but we were supporting a custom ATS for a customer where we had this perfect storm happen.
- We had a bug in it that we sorted out eventually, where sometimes when you fed it input that contained weird characters, it would cause the name of a function or variable to get echoed in the nearby output. So if you had a variable called $debug_page or a function called $send_to_processing, and you input say some Arabic characters (this customer had many job applicants who were native Arabic speakers) you might get output that was the output you wanted + that string so
Searching... 10 applicants found debug_pageorApplicant: Mohammad Al-Saud send_to_processing.- We had this developer who named things in lolcat speak. So a function might be called $ICanHaz($applicant) or $LongStringIsLong($string).
So we got an email from the customer saying they had a VERY offended job applicant and what had happened. They had clicked the reject button on someone, which triggered the system to send an automatic rejection form letter to the applicant. This applicant had some Arabic character in their last name, which triggered the bug.
And the reject applicant function had been written by this guy. So that poor applicant got an email that said
Dear Applicant
We have reviewed your application and while we thought you have an excellent background unfortunately we decided you are not a good fit for our company at this time… blah blah blah etc…
YouCanHazNoJobKThanksBai
I spent a disturbing amount of time figuring out why I didn’t get a video output.
I had not configured DP on the monitor.
It wasn’t dirt on my monitor, it was a weird unicode character
3rd line support for a global IT brand you have heard of, on the kind of security product that people don’t like to mess with too much once it’s installed on their servers.
Bug had been in the tracker over 3 years when I joined, and had defeated anyone who tried it. Segfault that happened to only one customer, unpredictably, and only once or twice a year, and nobody could reproduce it.
After a few weeks of tracing the compiled code line-by-line I found a race condition in the teardown of an object. That’s not the silly part.
I wrote the patch for the version of the code the customer was running and was hailed as a mighty hero and everyone on the bus clapped etc. Then I went to forward-port the patch to the newer versions of the program and… it was already fixed there. Some fucken doofus had either fixed the bug without realizing, or, fixed it and just skipped the standard backporting process that would normally patch all the other versions that were still in support.
Forgot to save. You ever spend 45 minutes looking for a bug you already fixed?
Or variations of this caused by a makefile not having correct dependencies set up, eg it points to dependent source files but not the headers so header updates get ignored during compiles. Made me add a “make clean” step to the debug process of “change that should have fixed the issue appears to be doing nothing at all” issues, or even just defaulting to rebuilding everything because test times can take hours or even days to get to the issue, so I don’t want to waste that much time only to find out it’s still running the old version.
Yep. Last time I used MS Visual Studio it was still all too eager to run an older binary, and I lot plenty of time debugging a binary that doesn’t reflect the current code. And, even more recently, when testing requires you to remember to run separate routines to upload to a testing server and restart a service, it is really easy to forget to do that when you are bouncing between the code and the browser console to figure out what to change.
My system didnt boot for obscure reasons
Found out something had caused my nix store (packages) to explode in size. Chrooting didnt work as it was filled to the last byte. Deleted some files, then chrooted in and did a cleanup
One time I was struggling to understand why a code branch I wrote was being unexpectedly taken, and I found that I had written something like
if pet == 'cat' || 'dog'. Since'dog'was a string, the condition was always true. I laughed out loud at myself.A static type system can be used to make this type of error occur at compile-time rather than runtime. But, not everyone wants to make that tradeoff and some even like the semantics applied to that kind of expression.
||often gets tasked with handlingnull/undefinedin JS, e.g.
Back when I was learning c++ on Windows, I naively jumped right into game dev (as one does) before understanding the purpose of a debugger. I spent 3 months chasing down a period that should have been a comma. Due to function overloading, this was not an error or warning. It’s just silently calling the wrong function and crashing the program.
Thus began my distrust of magic compiler features. To save typing a handful of characters, languages add new ways to blow off your own leg. Every time you blow off your leg, the time you lose is orders of magnitude greater than just being explicit. Just read this thread for more examples. Today, I program almost exclusively in C. I have no desire to use more feature-rich/higher level languages for anything.
ECU (the computer in your car) only came online on the bus at every 3rd restart. No memory was written, yet the bastard somehow knew it anyway.
Turns out the transciever’s enable pin was left unconfigured and supposedly some charge accumulated during two startups to set it.
Love this
Goddamn case sensitive POS JavaScript.
I can’t quite remember what I was debugging exactly, some constant was different in runtime compared to what was in code. Someone added a leading 0 to a const int to make the number align with others in terms of character count just to make it pretty I guess. That is when I learned about octal literals in C. I think that was the only time I’ve seen one in many years and it was used unintentionally. To save you a search leading 0 in C makes number to be base 8 same as 0x makes it hex aka base 16, so that inconspicuous 01000 is not a 1000 it’s a 512.
It’s one of the most sneaky legacy foot-guns C (and C-like languages) have. I think we’re decades removed from using octal everywhere, except for Linux filesystem flags (which the letter-equivalents should probably be used instead).
Haha, I always love that one when I debug some other codebase
This was dumb, and it was on me.
Couldn’t figure out why two obscure software packages were erroring in a very particular way. Thinking there was no way in hell a search would help, I plugged it in Google. There was user on Spiceworks outlining my exact situation and fix. Who is this mad genius?!
It was me. I fixed it two years previously and went back to note so in the forum.
Would have been even more hilarious if your previous fix was hidden by a “nm, I figured it out” update.
The one and only denvercoder?
Internet Explorer didn’t automatically have “console.log” defined until you opened the console window. So there was an error breaking the web page that would disappear when you tried to open the console to see the error. The error was that console.log wasn’t defined. Fucking IE.
That would genuinely make me clock the fuck out for the day when I figured it out, jesus christ.
/thread, holy shit lmao
I fixed a 5 year old issue that the previous guy claimed was “unfixable”. Turns out it was because someone copy-pasted a value from an Outlook email…and it had a single dash in it…which outlook converted to a double dash.
That’s why I was so confused about the AI emdash connection. MS Office has been replacing dash with emdash for 20+ years.
I was confused too. But now I think it’s specifically em dashes in the middle of words, isn’t it? Like copy—paste instead of copy-paste?
I have had issues of having the same characters but in Unicode failing. But if I type it manually or paste it into Notepad++ forcing it to ASCII first, it works.
Person before flipped a bunch of if checks to put the value before the variable (if 6==x rather then if x==6). They messed up a bunch of the <= and >= checks by forgetting to reverse them. I improved performance and fixed numerous bugs by tracking those down.
Ah yes, yoda conditionals. Because guarding against accidentally typoing
if(x=6)is worth destroying your code’s readability.This is not needed anymore thanks to compiler warnings
Tell that to my colleague who still insists on writing if conditions like that. Maybe it’s just a PHP thing.
I think php had a linter for stuff like this. Defensive programming is good, but having tools to do the defending is better so I can use my brain power where it matters








