this post was submitted on 19 Nov 2026
196 points (99.5% liked)

Programmer Humor

34233 readers
1427 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 3 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] MECHASQrL@lemmy.world 28 points 2 days ago (2 children)

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).

[–] bitfucker@programming.dev 2 points 1 day ago

Haha, I always love that one when I debug some other codebase