15年后,微软合并了我的图表。
15 years later, Microsoft morged my diagram

原始链接: https://nvie.com/posts/15-years-later/

文森特·德里森(Vincent Driessen),2010年广受欢迎的“成功的Git分支模型”图表的作者,发现微软在其Learn门户上发布了一个由AI生成的、质量极差的他的作品版本。德里森一直欢迎他人分享和改编他的图表,但这次感觉不同——这是一种粗心、未署名的复制,缺乏原始图表清晰度和设计感。 AI版本充斥着错误,包括令人啼笑皆非的拼写错误(“continvoucly morged”),并迅速在网上引发了对公然剽窃的愤怒。德里森对图表本身的使用并不介意,而是对过程感到不满:将经过深思熟虑的作品用AI降级,并将其作为原创内容呈现。 他担心这一事件凸显了一个更大的趋势——越来越多地使用AI生成内容,而没有署名或质量控制,这可能会使未来更难识别和解决知识产权盗窃问题。他请求一个简单的链接回到他的原始文章,并希望了解微软的流程。

这次黑客新闻的讨论围绕微软似乎抄袭了开发者cheeaun创建的图表,但有一个奇怪的转折:一个AI工具将“continuously merged”(持续合并)误解为“continvoucly morged”,而这个修改后的短语出现在了新版本中。 许多评论者指出,在领英等平台上,AI生成内容的趋势日益增长,用户正在使用ChatGPT“改进”现有作品,但经常产生毫无意义或不准确的输出,且未经审查就发布。这助长了由商业影响者激励下的大量类似低质量内容的涌现。 这起事件引发了关于检测AI驱动的抄袭越来越困难的争论,因为工具变得越来越复杂,并且对微软等大型企业普遍持愤世嫉俗的态度,一些人指出它们有类似行为的历史。而“morged”这个词,源于AI的错误,正在作为描述这种类型AI辅助内容创作的术语而流行起来。
相关文章

原文

A few days ago, people started tagging me on Bluesky and Hacker News about a diagram on Microsoft's Learn portal. It looked... familiar.

In 2010, I wrote A successful Git branching model and created a diagram to go with it. I designed that diagram in Apple Keynote, at the time obsessing over the colors, the curves, and the layout until it clearly communicated how branches relate to each other over time. I also published the source file so others could build on it. That diagram has since spread everywhere: in books, talks, blog posts, team wikis, and YouTube videos. I never minded. That was the whole point: sharing knowledge and letting the internet take it by storm!

What I did not expect was for Microsoft, a trillion-dollar company, some 15+ years later, to apparently run it through an AI image generator and publish the result on their official Learn portal, without any credit or link back to the original.

Close-up of the "continvoucly morged" text

The AI rip-off was not just ugly. It was careless, blatantly amateuristic, and lacking any ambition, to put it gently. Microsoft unworthy. The carefully crafted visual language and layout of the original, the branch colors, the lane design, the dot and bubble alignment that made the original so readable—all of it had been muddled into a laughable form. Proper AI slop.

Arrows missing and pointing in the wrong direction, and the obvious "continvoucly morged" text quickly gave it away as a cheap AI artifact.

It had the rough shape of my diagram though. Enough actually so that people recognized the original in it and started calling Microsoft out on it and reaching out to me. That so many people were upset about this was really nice, honestly. That, and "continvoucly morged" was a very fun meme—thank you, internet! 😄

Oh god yes, Microsoft continvoucly morged my diagram there for sure 😬

Vincent Driessen (@nvie.com) 2026-02-16T20:55:54.762Z

Other than that, I find this whole thing mostly very saddening. Not because some company used my diagram. As I said, it's been everywhere for 15 years and I've always been fine with that. What's dispiriting is the (lack of) process and care: take someone's carefully crafted work, run it through a machine to wash off the fingerprints, and ship it as your own. This isn't a case of being inspired by something and building on it. It's the opposite of that. It's taking something that worked and making it worse. Is there even a goal here beyond "generating content"?

What's slightly worrying me is that this time around, the diagram was both well-known enough and obviously AI-slop-y enough that it was easy to spot as plagiarism. But we all know there will just be more and more content like this that isn't so well-known or soon will get mutated or disguised in more advanced ways that this plagiarism no longer will be recognizable as such.

I don't need much here. A simple link back and attribution to the original article would be a good start. I would also be interested in understanding how this Learn page at Microsoft came to be, what the goals were here, and what the process has been that led to the creation of this ugly asset, and how there seemingly has not been any form of proof-reading for a document used as a learning resource by many developers.

Till next 'tim'.

联系我们 contact @ memedata.com