People have been memeing about this part of a flowchart from this microsoft blog about some bullshit github feature all day and it's still up at the time of posting.
So evidently nobody at microsoft has figured out how to fucking edit an image at this point.
@munin "It's morgin time!!"
@munin I've always hated morging into traffic
@munin that’s definitely an AI artifact. It’s impossible to get copilot to make any kind of image with accurate text labels.
@munin MS Vibesio; for when the diagram clearly isn't worth the trouble.
To my mind the real prize in this diagram is the Timm line. (Alas that mere text can not reproduce that three-hooped m.)
Note that the new standard Git development flow evidently involves moving backwards in time, I mean Timm. Very impressive!
"It's morging time!"
@munin I love the English language! Ever-evolving with so many new verbs and terms. In this instance, I’ll gladly begin to employ “to morg” because, based purely on context, it seems to be defined as
morg / mɔrg /
verb
a deadly or grossly negligent outcome upon merge.
To use it in an example:
After the changes were shipped, they published just before the failover and morged the live which resulted in the 2:12AM outage for the on call.
@munin This looks suspiciously like an AI error.
@munin CI/CD: continuous intelligence, continuous degradation
@munin probably someone didn't save the Visio diagram as a Visio document and just shat out the .jpg so they can't just edit it.
Or they're so tight fisted that it's an internal licensing issue.
@munin a colleague of mine played around with the copilot built into PowerPoint to spice up her slides.
Turns out instead of giving you some objects you can then manipulate into what you really want, it just gives you an image.
Which is how you get shit like this - instead of being able to just edit the text, you’d have to completely recreate the whole thing by hand.
so literally worse than useless.
@munin yuppppp
I’m reminded of the person who a couple weeks ago figured out that just clicking “go away” to all the copilots was taking up a measurable amount of time. So doing things the same way they always did was taking longer. (And no time savings by using the tools because they can’t effectively do those tasks)
@munin
Yeah, that's not how you spell time, actually, that's not even unicode.
Whole thing was AI generated.
@munin New coding t-shirt: "MORGED TO RUN"
@munin to be fair I forget git options all the time so it's probably more accurate to say I "morged" the branches.
@munin you know, it’s gonna be hard for younger developers to carve through all the slop if they want to learn anything
There's no pipeline for them to get hired anyway at this point.
oh dear fucking gods it's been there since at least fucking December.
@munin Ha! I saw the flow chart and read the typo. didn't know it was from an official document.
there are multiple issues with the chart, with the garbled text being only the most obvious bit.
Clearly this is write-only content: something that was spewed out and no actual person ever looked at it.
We used to fucking call that spam.
@munin I used to look forward to GitHub blog posts because they would get deep into stuff that I found fascinating to learn about¹.
Looking at my RSS database history, it has been months since I even read anything GitHub has posted, other than their git release info roundups... but recently even those have gone weird². They don't even have one for 2.53 yet.
Next step is unsubscribing, I guess.
¹: e.g. https://github.blog/open-source/git/counting-objects/ / https://web.archive.org/web/20240912044358/https://github.blog/open-source/git/counting-objects/ , 2015-09-22
