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"
@dazfuller@mstdn.social in the top left there it doesnt even say time, its "timn"(???) the last latter of that isnt a real letter. i assume that means time but backwards bc the arrow is backwards
@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 plaguarises
(0 points, redo course next year, this is your one strike, as a TA, we have seen too many people try this.....)
@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 merge
Use 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.*
@aleciabatson @dazfuller @munin
Another: slopic or sloptic
A portmanteau in today’s social media rich environment
