This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

[alxndr@tech.lgbt]

@dazfuller Only bugfixes!

[dazfuller@mstdn.social]

@rhempel I tried to do the nice thing and filed an issue against it. Not holding my breath though, the last time I did that it was hanging around for 2 years until they deprecated it with a different product

[leo_wallentin@mastodon.social]

@ohmrun @dazfuller to be fair time travel often seems like the most viable option when git merges go wrong

[shadowdancer@mstdn.social]

@dazfuller
Now WTF seriously? I had to literally spell the domain out loud. Yes, it really is microsoft.com and not some parody site. It's not like I ever held Microsoft in high regard but this is beyond all comprehension.

Is there really no one doing any proofreading anymore? I mean, yeah they're in AI business and they use it themselves, but I wasn't aware they've literally taken hands off the wheel entirely.

[dazfuller@mstdn.social]

@shadowdancer I’m sure they said something about quality recently as well

Got to admit that I did the same as well. No way, I thought, they would take a well recognised and widely used image and fuck it up with AI. But, alas, this is where we are.

They’re now driving around a mountain, perilously close to the edge, blindfolded, and not holding the wheel.

[andrewradev@hachyderm.io]

@dazfuller This, to me, is a perfect encapsulation of the value proposition of chatbots: do what you can already do, but worse.

The original image is available on the author's blog as a high-resolution PDF, explicitly licensed as Creative Commons BY-SA. It is *trivial* to find the article and get the canonical image. Instead, somebody asked copilot to regurgitate one, or possibly asked it to "upscale" a low-res copy of it.

Doing the work well would have been faster and easier, but the vibe must flow.

[jsamcfarlane@mastodon.ie]

@dazfuller @rhempel TBF, it's made only slightly worse

[dazfuller@mstdn.social]

@JSAMcFarlane @rhempel I’m sure everyone who loves gitflow will come to its rescue

[dpnash@c.im]

@dazfuller > don't know why Tim is working in the opposite direction

It's not "Tim", it's "Timn" or "Tinm". No wonder everyone is confused. "Timn" is the one who's working backwards. The *real* Tim, who is working forwards and understands the details of `git morge --continvoucly`, already left for the day. The team will have to settle for a regular old non-continvoucal morge until Tim comes back and they can ask him for help.

[tmr232@mastodon.social]

@dazfuller this is painful...

[dazfuller@mstdn.social]

@dpnash oh shit, sorry Tim! You should have words with Timn tomorrow before he starts working from the initial commit

[dazfuller@mstdn.social]

@tmr232 this is the future. It’s because we don’t understand how to morge code that software development will be dead in 6-12 months.

Just don’t ask which 6-12 months

[johnofrobotz@mastodon.girolab.foo]

@dazfuller Honestly, I think Tinn took one look at this and is headed out the door.

[itgrrl@infosec.exchange]

@dazfuller ‍️

[sykora@tech.lgbt]

@dazfuller My favorite part is when Tim said it's morgin time and morged all over everyone

[bernardsheppard@mastodon.au]

@dazfuller this can all be fixed by cherry pitting morges and squash morging, or if you don't like squash, pumpkin morgues.

[jackeric@beige.party]

@dazfuller this... this... this is a pastiche of a beautiful diagram of a Git branching model published in the late 2000s and later disowned by its authors as obsolete in an era of continuous delivery

[jackeric@beige.party]

@dazfuller Look!
https://nvie.com/posts/a-successful-git-branching-model/

[tezoatlipoca@mas.to]

@dazfuller I'm showing this to my boss tomorrow as exhibit no one as why ai cannot document software properly or replace us technical writers.

[jennyfluff@chitter.xyz]

@dazfuller it gets better the more you try to understand the graph