This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.
-
@dazfuller this is painful...
@tmr232 this is the future. It’s because we don’t understand how to morge code that software development will be dead in 6-12 months.
Just don’t ask which 6-12 months
-
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.
-
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 My favorite part is when Tim said it's morgin time and morged all over everyone
-
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 can all be fixed by cherry pitting morges and squash morging, or if you don't like squash, pumpkin morgues.
-
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... this... this is a pastiche of a beautiful diagram of a Git branching model published in the late 2000s and later disowned by its authors as obsolete in an era of continuous delivery
-
@dazfuller this... this... this is a pastiche of a beautiful diagram of a Git branching model published in the late 2000s and later disowned by its authors as obsolete in an era of continuous delivery
-
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'm showing this to my boss tomorrow as exhibit no one as why ai cannot document software properly or replace us technical writers.
-
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@mstdn.social "On a scale of zero to Tim"
-
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 old-fashioned but I'm against morging.
-
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.
-
@JennyFluff
The things Tim has seen.
@dazfuller -
-
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.
They should try SourceMorge
-
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 as I shared with @munin
I love the English #language! Ever-evolving with new verbs and terms. (Now, with #slopification!) In this instance, I’ll gladly employ “to morg” because, based purely on context, it seems to be defined as
morg / mɔrg /
verb
to cause a deadly or grossly negligent outcome upon mergeUse in a sentence
*After the changes were shipped, they published just before failover and morged the live, resulting in an outage for the on call.* -
@dpnash oh shit, sorry Tim! You should have words with Timn tomorrow before he starts working from the initial commit
@dazfuller @dpnash Tinm or timn (I'm still not sure myself.) Is not bound by the law of entropy, and therefore has been made responsible for making any
git morgesthat need to occur in the past. I hope that clears things up. -
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
That reminds me, what happened to the original Learn Microsoft documentation??? Was it archived at least?? -
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.
“But surely, Eddington, your theory implies an ‘arrow of Tim’ that runs counter to your expectations?”
“Don’t call me Shirley.”
-
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 keeps on slipping, slipping, slipping
Into the future -
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.
@benrfairless I’m not going to disagree with my latest find @MattHatton : AI is mad cow disease for computers
️
