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.

[tsturm@famichiki.jp]

@munin New coding t-shirt: "MORGED TO RUN"

[munin@infosec.exchange]

@danschnau

There's no pipeline for them to get hired anyway at this point.

[rusty__shackleford@mastodon.social]

@munin @da_667

Yeah, that's not how you spell time, actually, that's not even unicode.

Whole thing was AI generated.

[da_667@infosec.exchange]

@rusty__shackleford @munin

[moar_powah@mstdn.social]

@munin Ha! I saw the flow chart and read the typo. didn't know it was from an official document.

[munin@infosec.exchange]

@moar_powah

there are multiple issues with the chart, with the garbled text being only the most obvious bit.

[tindrasgrove@infosec.exchange]

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

[munin@infosec.exchange]

@TindrasGrove

so literally worse than useless.

[tindrasgrove@infosec.exchange]

@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)

[rusty__shackleford@mastodon.social]

@da_667 @munin

Pwease impwement our neUwU major featue~

[algernon@come-from.mad-scientist.club]

@munin its pretty much https://nvie.com/posts/a-successful-git-branching-model/ ran through a slop machine.

I knew the graphics looked familiar.

[munin@infosec.exchange]

@algernon

lol, so it's plagiarism too?

go fucking figure.

[algernon@come-from.mad-scientist.club]

@munin [always has been.jpeg]

[virtulis@loud.computer]

@rusty__shackleford @munin @da_667 truly the stupidest Timmline possible

[goncalor@infosec.exchange]

@rusty__shackleford @munin also, did you notice that time moves forward as release numbers decrease? Wtf...

[tehfishman@ioc.exchange]

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

[paco@infosec.exchange]

@munin CI/CD: continuous intelligence, continuous degradation

[lemgandi@mastodon.social]

@munin This looks suspiciously like an AI error.

[caspicat@infosec.exchange]

@munin 9 months
https://github.com/MicrosoftDocs/learn/blob/main/learn-pr/github/introduction-to-github/media/2-git-flow-image.png

[aleciabatson@mastodon.social]

@munin I love the English language! Ever-evolving with so many new verbs and terms. (Now, with slopification!) 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.*