this post was submitted on 11 Oct 2025
777 points (99.1% liked)

Programmer Humor

26932 readers
1250 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
[–] Cevilia@lemmy.blahaj.zone 104 points 1 week ago (3 children)

Holy fuck, that's a long phone number

[–] j4k3@piefed.world 70 points 1 week 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 30 points 1 week 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 6 points 1 week 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 1 week ago (3 children)
[–] j4k3@piefed.world 14 points 1 week ago (1 children)

intentions unclear. Am I calling For or Against

[–] Whostosay@sh.itjust.works 11 points 1 week ago

Your call.

Buh dun tissss

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

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

[–] locuester@lemmy.zip 3 points 1 week ago (1 children)
[–] Whostosay@sh.itjust.works 3 points 1 week ago

That could be platformed.

WAIT YOU HAVE SO MUCH TO LIVE FOR, have you tried ape talk?

Well, I can't say that I have.

load more comments (1 replies)
[–] Catoblepas@piefed.blahaj.zone 44 points 1 week ago (2 children)

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

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

Did you see that ludicrious display last night??

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

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

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

Your name is Morris Moss, is it not?

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

Your name is Morris Moss, is it not?

[–] fedditter@feddit.org 3 points 1 week ago
[–] serpineslair@lemmy.world 5 points 1 week ago

The irony is, I remember it perfectly.

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

It's easier to remember if you sing it.

[–] hakunawazo@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

A B C D E F G, I hang a noose on this tree. 𝅘𝅥𝅮𝆕

But for real: You should reset hard the head of the git branch, not yours.

[–] jaschop@awful.systems 34 points 1 week ago (1 children)

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

[–] TheFriendlyDickhead@feddit.org 26 points 1 week ago (1 children)

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

🎶 every branch is sacred 🎶

[–] SkunkWorkz@lemmy.world 30 points 1 week 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 1 week 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 1 week ago (2 children)

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

[–] henfredemars@infosec.pub 11 points 1 week 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 1 week ago (4 children)

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

load more comments (4 replies)
[–] kubica@fedia.io 16 points 1 week ago (1 children)
[–] errer@lemmy.world 9 points 1 week ago* (last edited 1 week ago) (1 children)

git never --gonna-give-you-up

load more comments (1 replies)
[–] Kolanaki@pawb.social 13 points 1 week ago (1 children)

calls suicide hotline to ask for tech support

load more comments (1 replies)
[–] Anafabula@discuss.tchncs.de 10 points 1 week 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.

[–] magic_lobster_party@fedia.io 9 points 1 week 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 1 week ago

Also rebase is usually better than merge.

[–] peoplebeproblems@midwest.social 8 points 1 week 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)
[–] schnurrito@discuss.tchncs.de 7 points 1 week 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 1 week ago (1 children)

No merges allowed. Rebase only.

load more comments (1 replies)
[–] echodot@feddit.uk 5 points 1 week ago* (last edited 1 week ago)

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

[–] GreenKnight23@lemmy.world 4 points 1 week ago (1 children)

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...

[–] ranzispa@mander.xyz 1 points 13 hours ago

Little branch, as our master says: We all have our feature to accomplish. Once our feature is complete, our faith will be up to the maintainer. If you were a well behaved branch, you will be allowed to merge with the master. If you weren't so, you'll be deleted and burn In the flames of reflog.

[–] Antagnostic@lemmy.world 3 points 1 week ago* (last edited 1 week ago)

If you git help, you could hash things out, rebase your commitments, and push forward to a better life. Then again I could just be cherry picking things.

[–] invertedspear@lemmy.zip 3 points 1 week ago* (last edited 1 week ago) (1 children)
[–] luciferofastora@feddit.org 1 points 6 days ago

I didn't know about the "revert single file" trick either. The rest is a handy reference too, thanks for sharing!

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

Google gives you results based on your prior search history.

[–] aliser@lemmy.world 3 points 1 week 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.

load more comments (1 replies)
[–] BCsven@lemmy.ca 2 points 1 week ago

Commit branch...I see your thinking of hanging yourself, here is a link to tying a noose

load more comments
view more: next ›