this post was submitted on 11 Oct 2025
761 points (99.2% liked)

Programmer Humor

26846 readers
2426 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 2 years ago
MODERATORS
 
top 50 comments
sorted by: hot top controversial new old
[–] invertedspear@lemmy.zip 3 points 14 hours ago* (last edited 14 hours ago)

My best friend when I fuck a commit up: https://ohshitgit.com/

[–] Cevilia@lemmy.blahaj.zone 99 points 2 days ago (3 children)

Holy fuck, that's a long phone number

[–] j4k3@piefed.world 67 points 2 days ago (2 children)

It is a duplicated repeating error because this clownshow of a website is managed by squirrels and ducks. 1-800-273-8255 would be a valid US number. Doubling 273-8255 is not, but probably vibe coded under management that should be purged by these results.

[–] GreenShimada@lemmy.world 28 points 2 days ago (1 children)

Hey! Don't insult ducks like that! This clownshow website would be about 20% better if ducks were involved.

[–] j4k3@piefed.world 5 points 2 days ago

I don't know. I was cursing at ducks an hour ago while trying to remember how to spell diatomaceous earth and the ducks were total fuckwits.

[–] Whostosay@sh.itjust.works 6 points 2 days ago (3 children)
[–] j4k3@piefed.world 14 points 2 days ago (1 children)

intentions unclear. Am I calling For or Against

[–] Whostosay@sh.itjust.works 11 points 2 days ago

Your call.

Buh dun tissss

[–] locuester@lemmy.zip 6 points 2 days ago (1 children)
[–] Whostosay@sh.itjust.works 5 points 2 days ago (2 children)

Lmao not willing to do the phone math rn, does that actually fit the numbers?

load more comments (2 replies)
[–] eager_eagle@lemmy.world 2 points 2 days ago* (last edited 2 days ago)

It exists too, it seems to be a support line from British Columbia, CA

https://www.crisislines.bc.ca/services

[–] Catoblepas@piefed.blahaj.zone 44 points 2 days ago (2 children)

Well, that’s easy to remember! 0118, 999, 881, 999, 119, 725...3.

[–] fedditter@feddit.org 21 points 2 days ago* (last edited 2 days ago) (1 children)

Did you see that ludicrious display last night??

[–] OpenStars@piefed.social 14 points 2 days ago (1 children)

Yes I did. Just put it over there with the rest of the fire.

[–] kambusha@sh.itjust.works 7 points 2 days ago (1 children)

Your name is Morris Moss, is it not?

[–] fedditter@feddit.org 4 points 2 days ago (1 children)

Your name is Morris Moss, is it not?

load more comments (1 replies)
[–] serpineslair@lemmy.world 5 points 2 days ago

The irony is, I remember it perfectly.

[–] guillem@aussie.zone 11 points 2 days ago (1 children)

It's easier to remember if you sing it.

load more comments (1 replies)
[–] SkunkWorkz@lemmy.world 29 points 2 days ago

“Proper way to commit after merge conflict” sounds like a robot trying to save a relationship after a bad sex experience

[–] cupcakezealot@piefed.blahaj.zone 24 points 2 days ago (1 children)
git reset --hard <commit-hash>  
git push -f origin main  

i didn't see anything, officer

[–] martinb@lemmy.sdf.org 18 points 2 days ago (2 children)

You should be forcibly kept away from production systems...

[–] henfredemars@infosec.pub 11 points 2 days ago (2 children)

We had an intern do this once. We changed our server config to make sure it wouldn’t accept such operations.

load more comments (2 replies)
[–] joyjoy@lemmy.zip 3 points 2 days ago (1 children)

Never use --force. Always use --force-with-lease.

[–] enbiousenvy@lemmy.blahaj.zone 2 points 2 days ago (2 children)

I've mistyped that a couple of times to be --force-with-leash

[–] joyjoy@lemmy.zip 4 points 1 day ago

git push origin master --force-with-leash

Don't do that to your master.

[–] cupcakezealot@piefed.blahaj.zone 2 points 1 day ago* (last edited 1 day ago) (1 children)

only do that in puppygit (with consent)

[–] jaschop@awful.systems 33 points 2 days ago (1 children)

It's never too late to git merge --abort!

[–] TheFriendlyDickhead@feddit.org 23 points 2 days ago (1 children)

But abortion is murder?!?!?!?!?

🎶 every branch is sacred 🎶

[–] magic_lobster_party@fedia.io 9 points 2 days ago (1 children)

Keep your commits small. Merge often. That will reduce the likelihood of terrible merge conflicts.

If you’re not sharing your work with your team mates for a long time, then you’re setting yourself up for trouble.

[–] SpaceCowboy@lemmy.ca 4 points 2 days ago

Also rebase is usually better than merge.

[–] Kolanaki@pawb.social 13 points 2 days ago (1 children)

calls suicide hotline to ask for tech support

load more comments (1 replies)
[–] schnurrito@discuss.tchncs.de 7 points 2 days ago

I remember when similar screenshots circulated for how to tell if i am running jdk or jre, which is even more surprising.

[–] dream_weasel@sh.itjust.works 7 points 2 days ago (1 children)

No merges allowed. Rebase only.

[–] dream_weasel@sh.itjust.works 2 points 1 day ago

And if you can't figure out how to rebase, I definitely don't want you solving your own merge commit!

[–] kubica@fedia.io 15 points 2 days ago (1 children)
[–] errer@lemmy.world 9 points 2 days ago* (last edited 2 days ago) (1 children)

git never --gonna-give-you-up

load more comments (1 replies)
[–] aliser@lemmy.world 3 points 1 day ago (1 children)

git is like a minefield. stray away even a little bit from standard path and you are done for. I had git multiple times throw some obscure errors at me when trying some commands and then trying to undo/recover. how's "undo" is not a git command I don't understand.

[–] nialv7@lemmy.world 1 points 1 day ago

undo is a jj command ;)

[–] Anafabula@discuss.tchncs.de 10 points 2 days ago

Jujutsu (which is compatible with git) has a nice conflict resolution flow that doesn't break you workflow.

Conflicts are encoded into the commits, so that there is never a weird in between state that you have to deal with immediately before being able to do anything else.
Then you can use Jujutsu's easier history manipulation to resolve the conflict in the conflicted commits.

https://steveklabnik.github.io/jujutsu-tutorial/branching-merging-and-conflicts/conflicts.html

And you could always jj undo if you did something you didn't want to.

[–] echodot@feddit.uk 5 points 2 days ago* (last edited 2 days ago)

See I wasn't really going to kill myself today, but the thought of dialing that long ass number is just to much.

[–] peoplebeproblems@midwest.social 8 points 2 days ago (1 children)

Been there too OP. Not a good place.

It's usually easier to find another job, it will reset your mind, and fear won't be driving you.

Or you could just commit what you have, comment "YOLO" and auto resolve conflicts and push.

load more comments (1 replies)
[–] GreenKnight23@lemmy.world 3 points 1 day ago

in life you commit to many things. you commit to yourself, to your partner, to happiness, to legacy.

when we die, is that like a push to origin?

when we die, do our commits all go to the big repo in the sky?

is god the maintainer? when you pray is that like a bug report?

so many questions...

[–] dubyakay@lemmy.ca 3 points 2 days ago* (last edited 2 days ago)

Google gives you results based on your prior search history.

load more comments
view more: next ›