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
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Forgot to save. You ever spend 45 minutes looking for a bug you already fixed?
Back in the day not saving means you might lose your work during a crash. So ctrl-s after every change became habit even years into auto saving editors.
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.