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
And this is the figure from the 2010 blog post that their machine plagiarized (badly).
https://nvie.com/posts/a-successful-git-branching-model/ -
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 thank god we've finally found a use for all of those GPUs
-
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 I have no words ... what is the point of generating a slop version of an already existing image ?!!
How can we wake up of this nightmare !?
-
@dazfuller I think "morging" is one of those weird "sourcemaxxing" things all the cool kids are doing these days
I am Locutus of Morg. You will be assimilated 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 It's Tim Apple and he works in the opposite direction because he thinks different
-
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 Tirm keeps on slirping, slirping, slirping, into the future, or possibly, boats against the current, is borne back ceaselessly into the past
-
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 WHAT IS THAT VERTICAL ARROW? WHO IS TINM? NM ISN'T EVEN A DEFINED LIGATURE
(as far as I can tell)
(but it does exist maybe? maybe as a phonetic marker:
https://commons.wikimedia.org/wiki/File:Nm_ligature.svg
)
I am so confused
-
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 why do they never morg their severe bug fix...
-
@ohmrun @dazfuller It's Tiണ, or maybe Tiሰሰሰ
@bartholin @ohmrun @dazfuller Or is it? I think it's an nm ligature so it's Tinm.
-
@bartholin @ohmrun @dazfuller Or is it? I think it's an nm ligature so it's Tinm.
@bartholin @ohmrun @dazfuller AND IT HURTS EVERY TIME I LOOK AT IT
-
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 I will now pronounce "merged" as "morged" until my dying breath
-
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 is embarrassing, I will bitch internally
-
@dazfuller I will now pronounce "merged" as "morged" until my dying breath
@dazfuller also poor Tim. It's not his fault it's slop
-
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 the basic spelling mistakes make me think this might actually be a real person lol
-
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 Just one morge and Timn can parse XML with RegEx
-
@itgrrl @dazfuller Dank!
-
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
First thing I noticed was they used "master" vs "main" who would have thought a bunch of mostly white tech bros making LLMs would have reverted them 10 years in branch naming standards for all. -
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 and stolen from sources like https://nvie.com/posts/a-successful-git-branching-model/
-
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 Timm! featue! Microslop outdid itself
-
@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 @dazfuller there were so many ways for them to redo this graphic with very little effort, but nope, plagiarism machine plagiarises
(0 points, redo course next year, this is your one strike, as a TA, we have seen too many people try this.....)
️
