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

[dazfuller@mstdn.social]

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

I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

Components of the GitHub flow - Training

Learn to use the components of the GitHub flow

(learn.microsoft.com)

[tymwol@hachyderm.io]

Maybe it's a git mortgage, like the one you take for all this infrastructure and GPUs..?

[db@social.lol]

@dazfuller Tim is looking for an earlier sane commit before that mess to hard reset

[dazfuller@mstdn.social]

@db every time I look at it I find another layer of madness

[db@social.lol]

@dazfuller it is truly a masterpiece

[jdstewart2008@mastodon.social]

@dazfuller 3rd largest publicly-traded company in the U.S.

[ohmrun@indieweb.social]

@dazfuller That's Tim travelling back in time to fix his morge strategy.

[rhempel@mstdn.ca]

@dazfuller This is just GitFlow reinterpreted by AI and it's honestly pretty much why developers sometimes hate git

Move to Trunk Based Development (with a coach if you need it) and look back on this model and laugh like a maniac.

[loosenut@genart.social]

@ohmrun @dazfuller

That was the beginning of the great Tim wars, which continue to this day

[dazfuller@mstdn.social]

@rhempel I mean, it _should_ be gitflow, and yet the AI somehow made it more complicated and incorporated temporal dynamics

[bartholin@fops.cloud]

@ohmrun @dazfuller It's Tiണ, or maybe Tiሰሰሰ

[ohmrun@indieweb.social]

@loosenut behold the enborkening.

[rhempel@mstdn.ca]

@dazfuller It should have just been a link to the (awful) Gitflow image everyone uses.

Instead it's a clear demonstration of Microsoft eating its own AI dogfood, and finding out that it's rotten, and they don't have the common sense to sniff it before eating it.

They have really lost the thread ...

[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