this post was submitted on 25 Jan 2025
702 points (98.1% liked)

Programmer Humor

33090 readers
343 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 7 points 5 days ago* (last edited 5 days ago) (1 children)

There's also "you forgot to save before you ran the compiler", and yeah, whatever is on that line in the stored to disk version is garbage.

[โ€“] [email protected] 2 points 3 days ago

That's the worst when your cycle time is very long. You fix a bug in the code, start your test running again and come back to check the next day only to see the exact same bug again and might think that your fix didn't work and something more esoteric is going on ("maybe it's a compiler or hardware bug!" (It almost never is)).

Then you add a bunch of debug prints to really get a good idea of what's going on and rerun the test. Either you remembered to save and suddenly the mystery bug is gone because the fix is still in the code. Or maybe you forgot to save again and now it looks like it's not even reaching any of the code you added the prints to.