@thomasfuchs Separately from the insanity of publishing this at all, I'm almost certain this is a plagiarized regurgitation of a graph that appeared in a blog post several years ago. I remember quite clearly seeing this style in an article that discussed different ways of structuring git developement and release management. I wouldn't be surprised if, ignoring the text fails, this is a straight rip-off of one of those graphs. And if it's not structurally a rip-off, it's certainly plagiarizing the style.

(Edit: sorry, I now see that someone else has pointed this out already)

@thomasfuchs They replaced it. Fortunately, the Internet Archive has a couple copies of the old article (I added one).

@thomasfuchs can we also speak about how only an idiot would develop with this flow? Let's ignore the deepdream chart. Even if they had managed to communicate this idea clearly, the idea itself is badly flawed! The hotfix never gets released. Also, the only people I've met who would use the word "hotfix" were all dangerously stupid people.

@thomasfuchs Reading this graph went like this in my mind :

- I don't see what the fuss is about, this looks like a pretty classic git flow
[...]
- Wait, wat ?
[...]
- Oh no
[...]
- Oh no
[...]
- Oh no

And the more you look at it, the worse it gets

@thomasfuchs this is stolen from here

https://nvie.com/posts/a-successful-git-branching-model/

It has nothing to do with AI, it was created by a human in 2010.

@thomasfuchs This is a plot diagram of the movie Looper. It did not end well for Timn.

@thomasfuchs@hachyderm.io Bad OCR / image generation fail. It's clearly the git flow method. I think they were trying to morge this: https://nvie.com/posts/a-successful-git-branching-model/

@thomasfuchs You're not wrong about this but, I mean, it's Microsoft.

Stuff that looks like this is their jam.

@thomasfuchs looks suspiciously similar to this https://jeffkreeftmeijer.com/git-flow/

@thomasfuchs And Nadella wants us to stop calling this slop 🤷‍♂️

@thomasfuchs $ alias morge="git merge"

@thomasfuchs $ alias morge="git merge"

@thomasfuchs "The Dyslexia of Graphics"

@thomasfuchs you know what this reminds me of? i collect random bootleg items and often times they use flavor text stolen from other things, and then retyped manually by people who don't speak english. so you end up with shit like this:

@thomasfuchs @edeverett Best diagram to explain “continvoucly morging” IMHO

@thomasfuchs The “Time”(?) axis is labelled “Tiꦟ”…?

@thomasfuchs They changed the image on the site, but it’s still available here: https://web.archive.org/web/20260216165612/https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow

@thomasfuchs

Omg i was so confused until I read the alt-text

@thomasfuchs what the actual fuck is that! rhetorical question of course, we all know what it is, it is a pile of crap.

@thomasfuchs Does the existence of pictures like this indicate how most people never try to read and understand charts?

When this exists, they will never learn that it's worth making the effort :(

@thomasfuchs

"What do you call yourselves?"
"The Aristocrats"

@thomasfuchs

I'm going to be morging my changes back to the develop branch from now on!

@thomasfuchs appears to have been silently replaced within the last ~10 minutes, i just opened the page again to grab a screenshot and there's a new diagram where that one was

@thomasfuchs if I were @nvie I'd partner up with an attorney specialised in copyright and sue the f**k out of them

@thomasfuchs I've always wondered how plumbuses were made

@thomasfuchs even gitflow is too complicated for most projects, and that doesn't even involve morging

@thomasfuchs When did they release this? And what's Tim up to? I guess he's past the top of the chart? I have enough trouble understanding these when they are well formatted, but um, what's Tim doing up, and arrows pointing down?

@thomasfuchs This looks like a derivative of the original, which I believe is here: https://jeffkreeftmeijer.com/git-flow/

@thomasfuchs Cc @davidgerard

@thomasfuchs I love continvoucal integration, i can just morg my featues without worries

@thomasfuchs did they just take the original (https://nvie.com/posts/a-successful-git-branching-model/) and run it through an image generator?

@thomasfuchs the longer I look the worse it gets. “Tim” had me laughing but then I looked at where they put release branches and how they ordered the tags… I am so confused.

@thomasfuchs

https://phpc.social/@paulshryock/116049285255396442

@thomasfuchs yikes

@thomasfuchs What letter is that? 😜

@thomasfuchs wtf

@thomasfuchs this is what happens when you1 feed git-flow and github's own docs through a plagiarism machine.

1. microslop ↩︎

@thomasfuchs

What am I even looking at? 😭

What the heck is this?

Source: https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow

@thomasfuchs what is Tim doing on the left side?

@thomasfuchs I still have that book, probably bought it at the same time as you.

As to the graph, I bet the severe bug was a side effect of that branching.

@thomasfuchs Explain?