This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
-
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.
-
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 How about that new "featue" introduced?
-
@dazfuller How about that new "featue" introduced?
@dusoft OMG I missed that one! This just keeps giving
-
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 This s/video conference/image/ could have been a s/email/SVG/
-
@dazfuller
And this is the figure from the 2010 blog post that their machine plagiarized (badly).
https://nvie.com/posts/a-successful-git-branching-model/@jedbrown @f4grx @dazfuller Ah, that Tim...
-
@dazfuller Just one morge and Timn can parse XML with RegEx
@qwertziop No way, only Chuck Norris can do that! But Timn will morge anyway even if it doesn't work, won't he? @dazfuller
-
@qwertziop No way, only Chuck Norris can do that! But Timn will morge anyway even if it doesn't work, won't he? @dazfuller
@quincy @qwertziop Timn is the result of a failed morg attempt
-
@quincy @qwertziop Timn is the result of a failed morg attempt
"AI makes mistakes. So what, it's not a bug, it's a featue!"
-
@axoneko that’s a pretty decent write up. Though, like Microslop, I think Morg as a verb is likely to stick around for a while yet.
I do love the idea of an urban dictionary style site tracking these new terms which are attributed to AI slop
-
P pelle@veganism.social shared this topic
