This was from official Microslop documentation https://web.archive.org/web/20260216165612/https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow
Remember when morgius morged all over those guys?
git Morge perfec t flow for put code in to re\lease! inside very Bronch and Featue code morge continvoucly put code in Git Morge. no problems ever in gitt morge because good Flow and Barnch for code morge conflict of big code releas. Agit Morge yes a place for a code put code in git morge can trust Tirm for giveing good morge to code. friend morge
Wish I hadn’t read this while drinking my tea.
I know this is a meme but what is it from
I based it on the pelcan Mouth perfec t size for put baby in pasta
Thats the one, thank you!
No worries! pelcan Mouth perfec t meme for make snowclone of.
:3
To be honest, what I’m most mad about isn’t the typoes, it’s that someone generated this image and figured, yeah alright, that will clear things up.
On some level you want to believe that even if someone does not come up with a proper concept for a visualization, that they still check what the AI shat out, so that it’s at the very least not conceptually wrong and not confusing.
This image isn’t just shitty, it’s actively worse than having no visualization. They could’ve generated that, chuckled, and not used it. Just how do you blunder your perception check so badly that you decide to include it anyways?
There is the decades-old adage:
Incorrect documentation is worse than no documentation.
That’s why I never comment my code. The documentation is in the
.hfiles. The “h” means “help”.In my company the h means “haha, what were you expecting?”
I really hope “morging continvoucly” becomes a meme and is used to mock microsoft forever
I for one will use it continvoucly.
Well, that explains a lot about the product quality. Their entire development workflow is a complete fucking mess.
- Long-lived feature branches.
- Creating merge commits to main just for the sole purpose of tagging them as releases while also maintaining separate release branches.
- Force-pushing tags to incorporate post-release hotfixes instead of releasing minor patch updates.
- Taking bugfixes from releases and merging them back into the development branch (have they not heard of
cherry-pick?) - Always using merges even when a rebase would be easier to follow and keep the history more straightforward.
Major featue UwU
And Microsoft stole it from a different developer, who posted it back in 2011… and then ran it through Copilot without even checking it thoroughly before adding it to training documentation.
I feel it’s a bad sign that I’m saving this meme for use at work
Everybody has a testing environment. Some people are lucky enough enough to have a totally separate environment to run production in.
Thank god we are going opposite to the Tim direction
Tirm
Yeah, Fuck Tim
The 15yo “source” for the sloppy plagiarism: https://nvie.com/posts/a-successful-git-branching-model/
You gotto love how the AI took the axis on the left, was confused enough from its tail that it thought it must be pointing in the opposite direction to development flow and then went “welp if it is going in the other direction, the label “time” must be a typo. Ima make it Tim the time traveller instead”. Ofcourse none of it happened like this, but I would like to imagine that it did.
