this post was submitted on 17 Feb 2026
129 points (99.2% liked)

Programmer Humor

29805 readers
1078 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
all 23 comments
sorted by: hot top controversial new old
[–] balsoft@lemmy.ml 2 points 1 hour ago

I really hope "morging continvoucly" becomes a meme and is used to mock microsoft forever

[–] pivot_root@lemmy.world 3 points 1 hour ago

Well, that explains a lot about the product quality. Their entire development workflow is a complete fucking mess.

  • Long-lived feature branches.
  • Creating merge commits to main just for the sole purpose of tagging them as releases while also maintaining separate release branches.
  • Force-pushing tags to incorporate post-release hotfixes instead of releasing minor patch updates.
  • Taking bugfixes from releases and merging them back into the development branch (have they not heard of cherry-pick?)
  • Always using merges even when a rebase would be easier to follow and keep the history more straightforward.
[–] RustyNova@lemmy.world 4 points 2 hours ago

I love git flow but the GitHub tooling is bad. It forces you into GitHubflow which is very confusing for those building from source

[–] First_Thunder@lemmy.zip 37 points 5 hours ago (2 children)

Thank god we are going opposite to the Tim direction

[–] lonesomeCat@lemmy.ml 3 points 4 hours ago

Yeah, Fuck Tim

[–] princess@lemmy.blahaj.zone 15 points 4 hours ago* (last edited 4 hours ago) (1 children)

git Morge perfec t flow for put code in to re\lease! inside very Bronch and Featue code morge continvoucly put code in Git Morge. no problems ever in gitt morge because good Flow and Barnch for code morge conflict of big code releas. Agit Morge yes a place for a code put code in git morge can trust Tirm for giveing good morge to code. friend morge

[–] JetpackJackson@feddit.org 2 points 3 hours ago (2 children)

I know this is a meme but what is it from

[–] goatinspace@feddit.org 1 points 25 minutes ago

From 1985 when plutonium was pure and future considered 2015.

[–] princess@lemmy.blahaj.zone 1 points 3 hours ago (1 children)
[–] JetpackJackson@feddit.org 1 points 1 hour ago

Thats the one, thank you!

[–] Gyroplast@pawb.social 26 points 5 hours ago (2 children)
[–] Skullgrid@lemmy.world 8 points 4 hours ago

holy fuck, it's basically the time I followed a tutorial for generating "a witch" for AI art, and ended up with a horribly mangled MTG card

[–] pizza_the_hutt@sh.itjust.works 3 points 4 hours ago (1 children)

It's still not a bad system if you have to support and provide bugfixes for multiple versions of software. However, if you only support the latest version and only create bug fixes and features based on the latest release or main branch, then git-flow is way overkill.

[–] lmmarsano@group.lt 7 points 3 hours ago (1 children)

It's an atrocious, pointlessly complicated system resulting in convoluted project histories prone to confusion. Trunk-based development with sensible tags of releases & hotfixes achieves the same thing without the junk complexity. Git flow isn't overkill, it's just ill-conceived.

[–] thesmokingman@programming.dev 1 points 4 minutes ago

This is a joke, right? OneFlow isn’t trunk-based development and is actually gitflow with different steps. I have yet to see any org actually use trunk-based development mostly because I’ve not seen cherry-picking from the trunk adopted at any large scale.

[–] goatinspace@feddit.org 9 points 4 hours ago (1 children)
[–] filcuk@lemmy.zip 2 points 3 hours ago (1 children)

I feel it's a bad sign that I'm saving this meme for use at work

[–] princess@lemmy.blahaj.zone 2 points 2 hours ago

Everybody has a testing environment. Some people are lucky enough enough to have a totally separate environment to run production in.

[–] jcorvera@quokk.au 5 points 3 hours ago

And Microsoft stole it from a different developer, who posted it back in 2011... and then ran it through Copilot without even checking it thoroughly before adding it to training documentation.

[–] Avicenna@programming.dev 1 points 2 hours ago

Tim is going backwards in time

[–] 0ops@piefed.zip 2 points 3 hours ago

Major featue UwU