This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
-
@JennyFluff
The things Tim has seen.
@dazfuller@ohmrun @JennyFluff@chitter.xyz @dazfuller attack ships on fire off the coast of Orion
-
@JennyFluff
The things Tim has seen.
@dazfuller@ohmrun @JennyFluff@chitter.xyz @dazfuller attack ships on fire off the shoulder of Orion...
-
@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.
@rhempel @dazfuller git good. AI bad. Microsoft bad. ESL bad
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller Tim could not continvoucly because he had to go covfefe.
-
@dazfuller @lp0_on_fire @munin Shakespeare’s name has experienced multiple spellings, so it’s expected other words might also have alternate spellings.
@aleciabatson @dazfuller @munin, true; how many of them are right?
In this case, if I see the word ending in ‘g’ (or ‘gue’), I'd default to expecting a hard ‘g’; if I see it ending in ‘ge’, soft ’g’, so I'm not thinking so much alternative spellings as different words (or different potential words).
(Yes, I'm ignoring various other pronunciation rules on the grounds that Danger! Here Be Rabbit Hole For Diving Into And Getting Lost In. Fun, isn't it.)
-
@ohmrun @JennyFluff@chitter.xyz @dazfuller attack ships on fire off the shoulder of Orion...
@synlogic4242
Wait, are we talking the Men In Black universe, here?
@dazfuller -
@synlogic4242
Wait, are we talking the Men In Black universe, here?
@dazfuller@ohmrun @dazfuller that is Blade Runner blasphemy!
-
@ohmrun @dazfuller that is Blade Runner blasphemy!
@synlogic4242
It's notable that blade runner didn't have any pocket universes that I'm aware of.
@dazfuller -
@dazfuller thanks! For a moment I thought I was falling for a hoax
-
@synlogic4242
It's notable that blade runner didn't have any pocket universes that I'm aware of.
@dazfuller@ohmrun @synlogic4242 it was a noticeable absence.
But I’m also now reciting the Tears in the Rain scene over and over in my head again
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller wait, this is a copy of the git flow graph on https://nvie.com/posts/a-successful-git-branching-model/ (the 2010 blog post introducing the git flow workflow)
-
@dazfuller wait, this is a copy of the git flow graph on https://nvie.com/posts/a-successful-git-branching-model/ (the 2010 blog post introducing the git flow workflow)
@jhominal it is, but “improved” by AI
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller MORGED.
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller timntravelers have an unfair advantage at morging, but what are we going to do about it?
-
@dazfuller timntravelers have an unfair advantage at morging, but what are we going to do about it?
@hko it’s hard to do anything, they just keep turning up continvoucly
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller some people get @b0rk to draw and write them documentation for git… others… just end up with slop.
-
@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.
@AndrewRadev @dazfuller ah, so this is a clear licence violation as well…
-
@dallo @jedbrown @dazfuller even to the latter I’m sceptic. (And yes, I’ve been there, my CVS repo is way older than that.)
-
@itgrrl @dazfuller cofeve!
@Nymnympseudonymm @itgrrl @dazfuller I was thinking “cdesign proponentsists” myself.
-
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"
Update:
It looks as though after 4-5 months the page has been updated, but if you want to see the image in situ still then the way back machine has you covered.
@dazfuller Tim comes from the future and knows that all the good intentions for the project are in vain. He goes backwards in time to understand why software so often fails.
But like many developers he looks for the problem in code, instead of speaking with people and so he also will fail in solving this mystery.
