1020
Bug Fixing (programming.dev)
top 50 comments
sorted by: hot top controversial new old
[-] Deceptichum@kbin.social 112 points 9 months ago* (last edited 9 months ago)

And the worst part is when it actually does and you have no fucking idea what went wrong before.

[-] MrCookieRespect@reddthat.com 30 points 9 months ago

The pc had the hiccups and now it's fine. Problem solved!

[-] ericbomb@lemmy.world 8 points 9 months ago

Some times my game engine needs a wake up run, then an actual run.

load more comments (1 replies)
load more comments (1 replies)
load more comments (1 replies)
[-] Pantrygheist@programming.dev 105 points 9 months ago

That's step zero: rule out black magic

[-] embed_me@programming.dev 59 points 9 months ago

Those damn cosmic rays flipping my bits

[-] blanketswithsmallpox@lemmy.world 9 points 9 months ago

Please tell me you look skyward, shake your fist and yell damn you!!!!

[-] CanadaPlus@futurology.today 5 points 9 months ago

I wonder if there's an available OS that parity checks every operation, analogous to what's planned for Quantum computers.

[-] Danitos@reddthat.com 4 points 9 months ago

Unrelated, but the other day I read that the main computer for core calculation in Fukushima's nuclear plant used to run a very old CPU with 4 cores. All calculations are done in each core, and the result must be exactly the same. If one of them was different, they knew there was a bit flip, and can discard that one calculation for that one core.

load more comments (1 replies)
[-] DragonTypeWyvern@literature.cafe 15 points 9 months ago

That feeling when it is, in fact, computer ghosts.

[-] KingBoo@lemmy.world 71 points 9 months ago

Me: "Hmm... No... No the code is good, it's the compiler that's wrong."

runs again

[-] Blackmist@feddit.uk 61 points 9 months ago

Yeah, but sometimes it works.

[-] Aceticon@lemmy.world 20 points 9 months ago

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)
[-] noddy@beehaw.org 9 points 9 months ago

Good luck figuring out why it sometimes doesn't work 🙃

[-] CanadaPlus@futurology.today 9 points 9 months ago

Mmm, race conditions, just like mama used to make.

[-] Octopus1348@lemy.lol 7 points 9 months ago* (last edited 9 months ago)

There was that kind of bug in Linux and a person restarted it idk how much (iirc around 2k times) just to debug it.

[-] crushyerbones@lemmy.world 6 points 9 months ago

This is 100% valid when dealing with code generation sometimes and I hate it

load more comments (5 replies)
[-] Peafield@programming.dev 45 points 9 months ago

The first is a surprise; the second is testing.

[-] xor@infosec.pub 35 points 9 months ago
[-] vamputer@infosec.pub 68 points 9 months ago

Hmm..you may be right. I'll get my Hispanic friend to run it and see if he gets the same result.

[-] aiden@lemm.ee 22 points 9 months ago
[-] gaston1592@feddit.de 27 points 9 months ago

ok, then we ship your machine.

[-] quantenzitrone@feddit.de 28 points 9 months ago

i sometimes do that so i can inspect the error messages on a cleared terminal

[-] winky9827b@lemmy.world 9 points 9 months ago

Sometimes I forget what I was looking for and have to restart the mental loop when doing this.

[-] PoolloverNathan@programming.dev 25 points 9 months ago

One of my old programs produces a broken build unless you then compile it again.

load more comments (1 replies)
[-] nieceandtows@programming.dev 24 points 9 months ago

Just had that happen to me today. Setup logging statements and reran the job, and it ran successfully.

[-] TurtleTourParty@midwest.social 20 points 9 months ago

I've had that happen, the logging statements stopped a race condition. After I removed them it came back...

[-] Hupf@feddit.de 11 points 9 months ago

Thank you for playing Wing Commander!

[-] gravitas_deficiency@sh.itjust.works 22 points 9 months ago
======== 37/37 tests passing ========
[-] OsrsNeedsF2P@lemmy.ml 12 points 9 months ago

That's when the real debug session begins

[-] lorty@lemmy.ml 11 points 9 months ago

Great time to find out your tests are useless!

load more comments (6 replies)
[-] Buttons@programming.dev 19 points 9 months ago

If that doesn't work, sometimes your computer just needs a rest. Take the rest of the day off and try it again tomorrow.

[-] BigBenis@lemmy.world 19 points 9 months ago

The crazy thing is that sometimes this just works...

[-] DirkMcCallahan@lemmy.world 18 points 9 months ago

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?

[-] LazaroFilm@lemmy.world 12 points 9 months ago

That and a make clean can work wonders.

load more comments (1 replies)
[-] Aceticon@lemmy.world 17 points 9 months ago

Well, duh! You need to use the right incantations!

[-] jerrythegenius@lemmy.world 15 points 9 months ago

I actually did this earlier today

load more comments (1 replies)
[-] Aria@lemmygrad.ml 14 points 9 months ago

Somehow higher than 0% success rate.

[-] reverendsteveii@lemm.ee 10 points 9 months ago

it's only dumb til it works

[-] attero@feddit.de 5 points 9 months ago

The definition of insanity is doing the same thing over and over and expecting different results.

[-] rockSlayer@lemmy.world 5 points 9 months ago

Sponsored by QA gang. Gotta make sure it's a 5/5 issue and not just a frequent issue

load more comments
view more: next ›
this post was submitted on 24 Jan 2024
1020 points (98.2% liked)

Programmer Humor

19589 readers
554 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 1 year ago
MODERATORS