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 3rd largest publicly-traded company in the U.S.
-
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's Tim travelling back in time to fix his morge strategy.
-
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 just GitFlow reinterpreted by AI and it's honestly pretty much why developers sometimes hate git
Move to Trunk Based Development (with a coach if you need it) and look back on this model and laugh like a maniac.
-
@dazfuller That's Tim travelling back in time to fix his morge strategy.
That was the beginning of the great Tim wars, which continue to this day
-
@dazfuller This is just GitFlow reinterpreted by AI and it's honestly pretty much why developers sometimes hate git
Move to Trunk Based Development (with a coach if you need it) and look back on this model and laugh like a maniac.
@rhempel I mean, it _should_ be gitflow, and yet the AI somehow made it more complicated and incorporated temporal dynamics
-
@dazfuller That's Tim travelling back in time to fix his morge strategy.
@ohmrun @dazfuller It's Tiണ, or maybe Tiሰሰሰ -
That was the beginning of the great Tim wars, which continue to this day
@loosenut behold the enborkening.
-
@rhempel I mean, it _should_ be gitflow, and yet the AI somehow made it more complicated and incorporated temporal dynamics
@dazfuller It should have just been a link to the (awful) Gitflow image everyone uses.
Instead it's a clear demonstration of Microsoft eating its own AI dogfood, and finding out that it's rotten, and they don't have the common sense to sniff it before eating it.
They have really lost the thread ...
-
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 Only bugfixes!
-
@dazfuller It should have just been a link to the (awful) Gitflow image everyone uses.
Instead it's a clear demonstration of Microsoft eating its own AI dogfood, and finding out that it's rotten, and they don't have the common sense to sniff it before eating it.
They have really lost the thread ...
@rhempel I tried to do the nice thing and filed an issue against it. Not holding my breath though, the last time I did that it was hanging around for 2 years until they deprecated it with a different product
-
@dazfuller That's Tim travelling back in time to fix his morge strategy.
@ohmrun @dazfuller to be fair time travel often seems like the most viable option when git merges go wrong
-
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
Now WTF seriously? I had to literally spell the domain out loud. Yes, it really is microsoft.com and not some parody site. It's not like I ever held Microsoft in high regard but this is beyond all comprehension.Is there really no one doing any proofreading anymore? I mean, yeah they're in AI business and they use it themselves, but I wasn't aware they've literally taken hands off the wheel entirely.
-
@dazfuller
Now WTF seriously? I had to literally spell the domain out loud. Yes, it really is microsoft.com and not some parody site. It's not like I ever held Microsoft in high regard but this is beyond all comprehension.Is there really no one doing any proofreading anymore? I mean, yeah they're in AI business and they use it themselves, but I wasn't aware they've literally taken hands off the wheel entirely.
@shadowdancer I’m sure they said something about quality recently as well
Got to admit that I did the same as well. No way, I thought, they would take a well recognised and widely used image and fuck it up with AI. But, alas, this is where we are.
They’re now driving around a mountain, perilously close to the edge, blindfolded, and not holding the wheel.
-
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, 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.
-
@rhempel I mean, it _should_ be gitflow, and yet the AI somehow made it more complicated and incorporated temporal dynamics
@dazfuller @rhempel TBF, it's made only slightly worse
-
@dazfuller @rhempel TBF, it's made only slightly worse
@JSAMcFarlane @rhempel I’m sure everyone who loves gitflow will come to its rescue
-
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 > 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.
-
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 painful...
-
@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.
@dpnash oh shit, sorry Tim! You should have words with Timn tomorrow before he starts working from the initial commit
-
@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
