c/programmer_humor · by state_electrician@discuss.tchncs.de · 169d

Morge continvoucly

This was from official Microslop documentation https://web.archive.org/web/20260216165612/https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow

343 points · 49 comments · view on lemmy.world

49 Comments

First_Thunder@lemmy.zip · 97 pts · 169d (2 replies)

Thank god we are going opposite to the Tim direction

princess@lemmy.blahaj.zone · 26 pts · 168d

Tirm

lonesomeCat@lemmy.ml · 8 pts · 169d

Yeah, Fuck Tim

Gyroplast@pawb.social · 80 pts · 169d (9 replies)

The 15yo "source" for the sloppy plagiarism: https://nvie.com/posts/a-successful-git-branching-model/

credo@lemmy.world · 37 pts · 168d

OP responded to the great Morge: https://nvie.com/posts/15-years-later/

Skullgrid@lemmy.world · 24 pts · 169d

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

Ephera@lemmy.ml · 12 pts · 168d

Wow, it stole it badly enough that it might not count as copyright infringement in court, but it also stole it badly enough that it isn't useful at all.

pizza_the_hutt@sh.itjust.works · 10 pts · 169d (5 replies)

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 · 13 pts · 168d (4 replies)

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 · 4 pts · 168d (3 replies)

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.

chunkystyles@sopuli.xyz · 5 pts · 168d (1 reply)

I pushed my team to use trunk based development. We did cherry-picks from trunk to release branches for a couple years with no issues. Since then, I've written a GitHub action that automates the cherry-picks based on tickets in the commit messages.

But even before the automation, it drastically improved our dev processes.

We weren't on Git Flow exactly, but it was a bastardized version of it.

Having used TBD successfully for like 5-6 years now. I can't imagine using Git Flow.

NigelFrobisher@aussie.zone · 2 pts · 167d

I dream of getting back to TBD.

draycs@lemmy.world · 3 pts · 168d

What is large scale to you? We have 100-200 developers doing something fairly close to trunk based development. Including cherry picking from trunk when possible (not always practical for sufficiently old release branches)

balsoft@lemmy.ml · 59 pts · 168d (1 reply)

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

criss_cross@lemmy.world · 23 pts · 168d

I for one will use it continvoucly.

Ephera@lemmy.ml · 53 pts · 168d (5 replies)

To be honest, what I'm most mad about isn't the typoes, it's that someone generated this image and figured, yeah alright, that will clear things up.

On some level you want to believe that even if someone does not come up with a proper concept for a visualization, that they still check what the AI shat out, so that it's at the very least not conceptually wrong and not confusing.

This image isn't just shitty, it's actively worse than having no visualization. They could've generated that, chuckled, and not used it. Just how do you blunder your perception check so badly that you decide to include it anyways?

Gyroplast@pawb.social · 31 pts · 168d (1 reply)

There is the decades-old adage:

Incorrect documentation is worse than no documentation.

That's why I never comment my code. The documentation is in the .h files. The "h" means "help".

Railcar8095@lemmy.world · 17 pts · 168d

In my company the h means "haha, what were you expecting?"

mcv@lemmy.zip · 12 pts · 168d

That is exactly the problem. I understand people using AI to make things. I don't understand blindly publishing AI slop without verifying it's correct.

Everybody using genAI has to understand that AI will often be wrong, and frequently ridiculous, and that it's up to you to ensure that what you deliver is correct.

And because nobody likes to review other people's work (most people are terrible and sloppy reviewers), it's better to put yourself in the center: have AI propose ideas or review the result, but you make the thing. That's how you ensure everything passes through your hands.

ZomieChicken@sh.itjust.works · 6 pts · 168d

In a proper PnPRPG/Tabletop RPG game, a truly spectacular blunder feels like a success to the person who failed. Walk into a bar and critfail both your Communications check, and the "Oh crap, I failed that badly. Can I save this by doing ______?" follow-up Communications check? You think you did fine, but now the entire bar thinks you are a truly crazy person, and treat you with respect only because they think you're going to shiv them in the neck if they get out of line.

Avicenna@programming.dev · 4 pts · 166d

That is likely because depending on AI makes you gradually less and less likely to cross-check and verify stuff. For some the whole appeal is the belief that they can get the answer/product they want in a second, ready to go out of the box and without having to spend any mental energy.

princess@lemmy.blahaj.zone · 46 pts · 169d (7 replies)

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

xep@discuss.online · 12 pts · 168d

Wish I hadn't read this while drinking my tea.

JetpackJackson@feddit.org · 6 pts · 168d (5 replies)

I know this is a meme but what is it from

princess@lemmy.blahaj.zone · 21 pts · 168d (3 replies)

I based it on the pelcan Mouth perfec t size for put baby in pasta

JetpackJackson@feddit.org · 6 pts · 168d (2 replies)

Thats the one, thank you!

princess@lemmy.blahaj.zone · 12 pts · 168d (1 reply)

No worries! pelcan Mouth perfec t meme for make snowclone of.

JetpackJackson@feddit.org · 5 pts · 168d

goatinspace@feddit.org · 3 pts · 168d

From 1985 when plutonium was pure and future considered 2015.

anhkagi@jlai.lu · 35 pts · 168d

Even without considering the typos, the diagram is incomprehensible with all these arrows pointing in every direction and textboxes placed randomly. I had to look at the original to understand it.

goatinspace@feddit.org · 29 pts · 168d (2 replies)

filcuk@lemmy.zip · 7 pts · 168d (1 reply)

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

princess@lemmy.blahaj.zone · 11 pts · 168d

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

pivot_root@lemmy.world · 28 pts · 168d (3 replies)

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.

figjam@midwest.social · 33 pts · 168d (1 reply)

Whats a merge? We be morging up here

A7thStone@lemmy.world · 24 pts · 168d

It's morgin time

Ephera@lemmy.ml · 24 pts · 168d

I admire your ability to interpret anything into this fucking picture...

jcorvera@quokk.au · 13 pts · 168d (2 replies)

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.

StellarSt0rm@lemmy.world · 4 pts · 168d (1 reply)

Makes me wonder how much of the training documentation is AI generated...

jcorvera@quokk.au · 4 pts · 168d

Considering their recent output?

Probably all the latest pubs.

Grail@multiverse.soulism.net · 11 pts · 168d

Remember when morgius morged all over those guys?

Slashme@lemmy.world · 10 pts · 167d