And the worst part is when it actually does and you have no fucking idea what went wrong before.
this post was submitted on 24 Jan 2024
1028 points (98.2% liked)
Programmer Humor
23122 readers
1280 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
founded 2 years ago
MODERATORS
load more comments
(1 replies)
That's step zero: rule out black magic
Those damn cosmic rays flipping my bits
Please tell me you look skyward, shake your fist and yell damn you!!!!
I wonder if there's an available OS that parity checks every operation, analogous to what's planned for Quantum computers.
load more comments
(2 replies)
That feeling when it is, in fact, computer ghosts.
Me: "Hmm... No... No the code is good, it's the compiler that's wrong."
runs again
Yeah, but sometimes it works.
It's even worse then: that means it's probably a race condition and do you really want to run the risk of having it randomly fail in Production or during an important presentation? Also race conditions generally are way harder to figure out and fix that the more "reliable" kind of bug.
load more comments
(1 replies)
Good luck figuring out why it sometimes doesn't work 🙃
Mmm, race conditions, just like mama used to make.
There was that kind of bug in Linux and a person restarted it idk how much (iirc around 2k times) just to debug it.
This is 100% valid when dealing with code generation sometimes and I hate it
load more comments
(5 replies)
The first is a surprise; the second is testing.
i sometimes do that so i can inspect the error messages on a cleared terminal
Sometimes I forget what I was looking for and have to restart the mental loop when doing this.
One of my old programs produces a broken build unless you then compile it again.
load more comments
(1 replies)
Just had that happen to me today. Setup logging statements and reran the job, and it ran successfully.
I've had that happen, the logging statements stopped a race condition. After I removed them it came back...
Thank you for playing Wing Commander!
======== 37/37 tests passing ========That's when the real debug session begins
The crazy thing is that sometimes this just works...
If that doesn't work, sometimes your computer just needs a rest. Take the rest of the day off and try it again tomorrow.
I often do this, but I always hit Ctrl-S before running it again. Shamefully, this probably works about 10% of the time. Does that technically count as changing nothing?
That and a make clean can work wonders.
load more comments
(1 replies)
Well, duh! You need to use the right incantations!
Somehow higher than 0% success rate.
it's only dumb til it works
Sponsored by QA gang. Gotta make sure it's a 5/5 issue and not just a frequent issue
The definition of insanity is doing the same thing over and over and expecting different results.
"Works in my environment."
My way: wrap it in a shell script and put a condition if exit status is not 0 then say "try clear the cache and run it again"
load more comments
(1 replies)
view more: next ›