This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

[dpnash@c.im]

@dazfuller > don't know why Tim is working in the opposite direction

It's not "Tim", it's "Timn" or "Tinm". No wonder everyone is confused. "Timn" is the one who's working backwards. The *real* Tim, who is working forwards and understands the details of `git morge --continvoucly`, already left for the day. The team will have to settle for a regular old non-continvoucal morge until Tim comes back and they can ask him for help.

[tmr232@mastodon.social]

@dazfuller this is painful...

[dazfuller@mstdn.social]

@dpnash oh shit, sorry Tim! You should have words with Timn tomorrow before he starts working from the initial commit

[dazfuller@mstdn.social]

@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

[johnofrobotz@mastodon.girolab.foo]

@dazfuller Honestly, I think Tinn took one look at this and is headed out the door.

[itgrrl@infosec.exchange]

@dazfuller ‍️

[sykora@tech.lgbt]

@dazfuller My favorite part is when Tim said it's morgin time and morged all over everyone

[bernardsheppard@mastodon.au]

@dazfuller this can all be fixed by cherry pitting morges and squash morging, or if you don't like squash, pumpkin morgues.

[jackeric@beige.party]

@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

[jackeric@beige.party]

@dazfuller Look!
https://nvie.com/posts/a-successful-git-branching-model/

[tezoatlipoca@mas.to]

@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.

[jennyfluff@chitter.xyz]

@dazfuller it gets better the more you try to understand the graph

[jennyfluff@chitter.xyz]

@ohmrun @dazfuller and don't forget to completely ignore your release branch after 1.0, from now on development gets morged to master. In the past. Because Tim flows backwards

[nymnympseudonymm@mstdn.science]

@itgrrl @dazfuller cofeve!

[gustodon@mas.to]

@dazfuller It's old-fashioned but I'm against morging.

[nymnympseudonymm@mstdn.science]

@dazfuller
Y'all will love this I bet

/ducks

Entire · A new developer platform is coming

We are going beyond repositories, building a developer platform where agents and humans can collaborate, interact, and grow. The birth of a new galaxy in this universe draws near.

(entire.io)

[ohmrun@indieweb.social]

@JennyFluff
The things Tim has seen.
@dazfuller

[gustodon@mas.to]

@itgrrl

[float13@masto.hackers.town]

@dazfuller

They should try SourceMorge

[aleciabatson@mastodon.social]

@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.*