this post was submitted on 22 Jun 2024
510 points (97.9% liked)

Programmer Humor

19544 readers
651 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
 
top 20 comments
sorted by: hot top controversial new old
[–] neo@lemy.lol 40 points 4 months ago (2 children)

"Is your computer connected to a power outlet? Yes? Could you please unplug it and plug it back in for me?"

[–] marcos@lemmy.world 12 points 4 months ago

It's a much larger problem when there are several different cables.

[–] BlueMagma@sh.itjust.works 2 points 4 months ago

Also: please check the other end of the cable, the one that isn't plug in the wall, yes that one, plugged on the screen, unplug and plug it back in please.

[–] AnarchoSnowPlow@midwest.social 37 points 4 months ago (1 children)

"the serial output from my test unit turns into garbage and it happens at completely random times!"

"Did you make sure they were plugged in all the way?"

"WHAT?!?! ARE YOU SUGGESTING I DON'T KNOW WHAT I'M DOING?!?!"

Some time later

"Yeah, it turned out to be the serial connection was loose."

[–] bitfucker@programming.dev 2 points 4 months ago (1 children)

It is worse in HW prototyping where sometimes loose wire is all over the place

[–] AnarchoSnowPlow@midwest.social 2 points 4 months ago

"Where does this green wire go?"

I appreciate HW engineers and techs. I'm not afraid of datasheets, circuit diagrams, or a mso and they're always patient enough to explain things to me so I can make the rocks behave. Or at least tell me how to go from diagram to board lol.

[–] Doombot1@lemmy.one 23 points 4 months ago

As someone that works writing firmware for SAS devices… it’s happened all too many times

[–] VisualBuilder4@lemmy.world 23 points 4 months ago (1 children)

That sounds like a classical OSI layer 0 problem.

[–] Album@lemmy.ca 16 points 4 months ago (1 children)
[–] 30p87@feddit.de 3 points 4 months ago

Layer 40320

[–] jubilationtcornpone@sh.itjust.works 18 points 4 months ago (1 children)

At a former job, there was one -- and only one -- lady in customer service who would actually reboot and do all the basic troubleshooting steps before calling IT. If we heard from her, we knew something was legitimately broken. Oddly enough, I'm married to her now. Best decision I ever made.

[–] SatouKazuma@programming.dev 4 points 4 months ago

Have you had to reboot her yet?

[–] aard@kyu.de 10 points 4 months ago

Did pretty much the same with a new server recently - spent ages debugging why it didn't find the SAS disks. Turns out, disks like to have power connected, and no amount of debugging on software level will help you.

[–] doingthestuff@lemmy.world 9 points 4 months ago (1 children)

Always turn it off and on again. Then check cable and physical connections, then start the real troubleshooting. I have fixed over a thousand computers as a hobby. So I'm no pro, but I know that much.

[–] qaz@lemmy.world 2 points 4 months ago

I have rebooted it more than 10 times, and have checked literally every other connection but somehow forgot to check the actual SAS cable.

[–] onlinepersona@programming.dev 6 points 4 months ago

Happens to the best of us🤣

I spent what felt like an eternity debugging a website because it wasn't updating. You gussed it, I was looking the build output of webpak in the wrong folder.

Anti Commercial-AI license

[–] JoMiran@lemmy.ml 5 points 4 months ago (1 children)
[–] RizzRustbolt@lemmy.world 3 points 4 months ago

So many dongle failures, and so many sprung tension latches.

[–] Norgur@fedia.io 3 points 4 months ago

I'd rather troubleshoot for days than try to reboot or check cables.

[–] fibojoly@sh.itjust.works 2 points 4 months ago

"Hello IT, have you tried turning it off and on again?" pause "Is it plugged in?" pause "You're welcome"