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

[dazfuller@mstdn.social]

@mapache just please don’t throw Tinm under the bus, it’ll disrupt the space time continuum

[simonf@mastodon.gamedev.place]

@dazfuller

Its rendering of ‘m’ in ‘Tim’ reminded me of Terry Pratchett’s line

“Nanny Ogg knew how to start spelling 'banana’ but didn’t know how you stopped “

[dazfuller@mstdn.social]

@thibaultmol @jackeric stole "and improved with AI"

[spodlife@sunny.garden]

@dazfuller
That chart has been a "featue" of the page since at least September 2025
https://web.archive.org/web/20250908220945/https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow

[dazfuller@mstdn.social]

@spodlife so either they've not listened to any feedback yet, or they're doubling down?

I guess we wait and see if any fixes get morged in

[dazfuller@mstdn.social]

Damn! Posted this yesterday as I found it funny, but nothing prepared me for the howling laughter I would get from the comments

[qccechris@mastodon.social]

@dazfuller Tim with and extra ∩

[dallo@pouet.chapril.org]

@jedbrown @dazfuller and it is not even good nowadays. Was by 2010 standard.

[doragasu@mastodon.sdf.org]

@jedbrown @dazfuller Indeed the slop machine can only make what already exists but worse.

[felipe@social.treehouse.systems]

@dazfuller @JennyFluff the funniest thing to me is how simple the original is to understand

[lettosprey@tech.lgbt]

@dazfuller People: "GIt is too complicated", Microsoft: "Not anywhere near enough!"

[avuko@infosec.exchange]

@dazfuller doesn’t the existence of Tim n suggests a range of integer Tims working on this?

[jedbrown@hachyderm.io]

@dallo
It was a nice diagram, but poor workflow even in 2010. The gitworkflows(7) man page was first written in 2008 and had clear rationale. I made this figure in that era to show the parallelism exposed by the workflow. As CI has become more robust, many projects moved away from having a 'next' as a throw-away integration branch, but it is a useful strategy especially if you want user feedback on experimental features before you commit to including them by merging to 'main' (formerly 'master').
https://git-scm.com/docs/gitworkflows
@dazfuller

[dallo@pouet.chapril.org]

@jedbrown @dazfuller In 2010, we were on svn, mercurial and, in my circle, TFS. Git with the nvie workflow was another level.

[volpeon@icy.wyvern.rip]

@dazfuller Looks like Microsoft changed the image in the last 15 min or so. ​​ It was still there when I opened the link earlier.

[dazfuller@mstdn.social]

@volpeon in both happy and disappointed. But at least it will always be in the Internet Archive

[mdione@en.osm.town]

@dallo @jedbrown @dazfuller I was using nvie in 2007-08 in a startup. Later, CVS (!!!) in 2012-15 in a big company

[srazkvt@tech.lgbt]

@dazfuller the more i look at it the worst it gets

[dazfuller@mstdn.social]

@mdione @dallo @jedbrown I was trying to think what I was using around 2010. But think it was a mix of svn and TFS. Though there might have been a couple of projects still on cvs. That was for a Fortune 500 company

[bencomp@code4lib.social]

@dazfuller the course page has been updated; I don't see this image in there.