Vincent Driessen drew his Git Flow diagram in 2010. It became one of the most reproduced images in software engineering — a color-coded branching model that showed up in textbooks, conference slides, and onboarding docs at thousands of companies. Driessen made it in Apple Keynote. He published it under Creative Commons. He would have said yes if anyone asked.
Fifteen years later, Microsoft's Learn portal published an AI-generated copy. The arrows pointed in wrong directions. The colors were off. And the label read "continvuocly morged."
Not "continuously merged." Continvuocly morged.
The word "Time" became "Tim." Feature branches became "featue" branches. The diagram's careful visual hierarchy — developed over weeks by a human who understood what each arrow meant — was fed through what appears to be a diffusion model and excreted as a bitmap with hallucinated text.
Driessen found out when people on Bluesky started tagging him. His response was measured but pointed: a trillion-dollar company ran his work "through a machine to wash off the fingerprints" and published the result on their official documentation portal. No attribution. No link. No acknowledgment that a human made the original.
Scott Hanselman, Microsoft's VP of Developer Community, called it the work of an "overzealous vendor." Microsoft quietly removed the image. They provided zero public comment to media.
The Company That Builds Copilot Can't Check Its Own Documentation
Here is the part that should bother you more than the plagiarism.
Microsoft owns GitHub. GitHub sells Copilot, which generates code for millions of developers. Microsoft sells Copilot across Office, Azure, Windows, and Dynamics. The company's entire growth narrative for 2026 is built on the premise that AI output is reliable enough to ship.
And their documentation team published "continvuocly morged" on an official learning portal without a single human noticing.
This is the same company that reported $13.8 billion in AI revenue in Q2 FY2026. The same company whose CEO told investors that Copilot is "changing the way every role in every business function is being carried out." The tools are supposedly good enough to write production code. They were not good enough to spell "merged."
The diagram wasn't buried in some auto-generated API reference. It was on Microsoft Learn, the canonical documentation platform for Azure, GitHub, .NET, and every other Microsoft developer tool. Millions of developers use it daily. Someone decided an AI-generated diagram was good enough for that audience, and nobody between that decision and publication caught the gibberish.
The Pattern Is Bigger Than One Diagram
Spotify's co-CEO Gustav Soderström said in February that the company's most senior engineers "have not written a single line of code since December." They use an internal system called Honk, built on Claude Code, to generate features from natural language prompts sent via Slack. Engineers review and merge. Fifty new features shipped in 2025 under this model.
Meanwhile, an Anthropic study from January found that developers using AI assistance scored 17% lower on coding comprehension tests. They completed tasks marginally faster. They understood what they built marginally less.
The Microsoft diagram is a documentation version of this phenomenon. Humans aren't just delegating the creation of work to AI. They're delegating the verification. The person who published the morged diagram didn't misunderstand Git branching. They never read the output. The quality check was "does it look like a diagram?" and the answer was yes.
Driessen called it "proper AI slop." He worries that future AI plagiarism will be harder to detect as the mutations become subtler. Right now the errors are funny — morged, Tim, featue. But diffusion models improve. Text rendering is already dramatically better in newer image generators. The next stolen diagram won't have misspellings. It will just have wrong arrows, and nobody will notice because nobody checks.
The Real Cost of Not Reading
Microsoft's documentation is a trust layer. When a developer follows a Microsoft Learn tutorial and deploys to Azure, they're trusting that the instructions are correct. The morged diagram didn't just embarrass Microsoft — it introduced a question: what else on Microsoft Learn was generated by AI and never verified?
The company hasn't answered. They removed one image and blamed a vendor. They didn't say how many other AI-generated assets are in their documentation pipeline. They didn't announce a review. They didn't explain what quality controls exist.
Driessen's diagram was drawn by hand because he understood what it meant. Every arrow encoded a decision about how code should flow between branches. An AI model doesn't understand branching strategy. It understands pixel patterns. The difference was invisible to whoever published it — which is exactly the problem.
"Morged" is funny. The thing it represents is not.
Top comments (0)