logoalt Hacker News

15 years later, Microsoft morged my diagram

625 pointsby cheeauntoday at 6:20 AM248 commentsview on HN

Comments

cwal37today at 6:44 AM

LinkedIn is also a great example of this stuff at the moment. Every day I see posts where someone clearly took a slide or a diagram from somewhere, then had ChatGPT "make it better" and write text for them to post along with it. Words get mangled, charts no longer make sense, but these people clearly aren't reading anything they're posting.

It's not like LinkedIn was great before, but the business-influencer incentives there seem to have really juiced nonsense content that all feels gratingly similar. Probably doesn't help that I work in energy which in this moment has attracted a tremendous number of hangers-on looking for a hit from the data center money funnel.

show 6 replies
m12ktoday at 9:05 AM

Regarding the original git-flow model: I've never had anyone able to explain to me why it's worth the hassle to do all the integration work on the "develop" branch, while relegating the master/main branch to just being a place to park the tag from the latest release. Why not just use the master/main branch for integration instead of the develop branch - like the git gods intended - and then not have the develop branch at all? If your goal is to have an easy answer to "what's the latest release?", you have the tags for that in any case. Or if you really want to have a whole branch just to double-solve that one use-case, why not make a "release-tags" branch for that, instead of demoting the master/main branch to that role, when it already has a widely used, different meaning?

It's a pity that such a weird artifact/choice has made its way into a branching model that has become so widely implemented. Especially when the rest of it is so sensible - the whole "feature-branch, release-branch, hotfix" flow is IMO exactly right for versioned software where you must support multiple released versions of it in the wild (and probably the reason why it's become so popular). I just wish it didn't have that one weirdness marring it.

show 8 replies
Animatstoday at 7:41 AM

This is so out of hand.

There's this. There's that video from Los Alamos discussed yesterday on HN, the one with a fake shot of some AI generated machinery. The image was purchased from Alamy Stock Photo. I recently saw a fake documentary about the famous GG-1 locomotive; the video had AI-generated images that looked wrong, despite GG-1 pictures being widely available. YouTube is creating fake images as thumbnails for videos now, and for industrial subjects they're not even close to the right thing. There's a glut of how-to videos with AI-generated voice giving totally wrong advice.

Then newer LLM training sets will pick up this stuff.

"The memes will continue" - White House press secretary after posting an altered shot of someone crying.

show 2 replies
QuiCasseRientoday at 1:15 PM

This is the type of diagram that horrified me.

It's a very very hard and time consuming task for dev to maintain hotfix for previous releases !

Yeah, easier for users, they don't have to care about breaking changes or migration guide. They just blindly update to the nearest minor.

But as the time goes on, the code for dev ends up being a complete mess of git branches and backports. Dev finally forgot some patches and the software contains a major security hole.

Dev ends by being exhausted, frustrated by its project and roasted by its users.

=> What I do : do not maintain any previous release but provide a strong migration guide and list all breaking changes !

users just have to follow updates or use another software.

I'm happy with it, my project has no debt code and more clean code.

rmunntoday at 7:09 AM

Similar story. I'm American but work and live outside the US, so I don't know how likely this would be if I had ordered from Amazon. But I ordered a rug for my sons' room from this country's equivalent to Amazon (that is, the most popular order-online-and-we-ship-to-you storefront in this country), and instead of what I ordered (a rug with an image showing the planets, with labels in English) I got an obviously AI-generated copy of the image, whose letters were often mangled (MARS looked like MɅPS, for example). Thankfully the storefront allowed me to return it for a refund, I ordered from a different seller on the second try, and this time I received a rug that precisely matched the image on the storefront. But yes, there are unscrupulous merchants who are using AI to sloppily copy other people's work.

show 1 reply
nippootoday at 6:43 AM

They've taken it down now and replaced with an arguably even less helpful diagram, but the original is archived: https://archive.is/twft6

show 4 replies
anonymous908213today at 7:11 AM

Microsoft employee (VP of something or other, for whatever Microsoft uses "VP" to mean) doing damage control on Bluesky: https://bsky.app/profile/scott.hanselman.com/post/3mez4yxty2...

> looks like a vendor, and we have a group now doing a post-mortem trying to figure out how it happened. It'll be removed ASAFP

> Understood. Not trying to sweep under rugs, but I also want to point out that everything is moving very fast right now and there’s 300,000 people that work here, so there’s probably be a bunch of dumb stuff happening. There’s also probably a bunch of dumb stuff happening at other companies

> Sometimes it’s a big systemic problem and sometimes it’s just one person who screwed up

This excuse is hollow to me. In an organization of this size, it takes multiple people screwing up for a failure to reach the public, or at least it should. In either case -- no review process, or a failed review process -- the failure is definitionally systemic. If a single person can on their own whim publish not only plagiarised material, but material that is so obviously defective at a single glance that it should never see the light of day, that is in itself a failure of the system.

show 14 replies
jezzamontoday at 6:41 AM

"continvoucly morged" is such a perfect phrase to describe what happened, it's poetic

show 6 replies
hansmayertoday at 8:28 AM

This is hilarious actually. I am starting to lean into "AI-dangerous" camp, but not because the chatbot will ever become sentient. Its precisely because of increasingly widespread adoption of un-reliable tools by the incompetent but self-confident Office Worker (R).

show 3 replies
tomberttoday at 9:04 AM

Is there a single thing that Microsoft doesn’t half-ass? Even if you wanted to AI generate a graph, how hard is it to go into Paint or something and fix the test?

I have been having oodles of headaches dealing with exFAT not being journaled and having to engineer around it. It’s annoying because exFAT is basically the only filesystem used on SD cards since it’s basically the only filesystem that’s compatible with everything.

It feels like everything Microsoft does is like that though; superficially fine until you get into the details of it and it’s actually broken, but you have to put up with it because it’s used everywhere.

show 1 reply
adzmtoday at 6:51 AM

> Till next 'tim'

It took me a few times to see the morged version actually says tiന്ന

show 1 reply
Brian_K_Whitetoday at 6:44 AM

Please let morged become a thing.

show 3 replies
xxrtoday at 7:51 AM

When I read the title, I thought "morg" was one of those goofy tech words that I had missed but whose meaning was still pretty clear in context (like a portmanteau of "Microsoft" and "borged," the latter of which I've never heard as a verb but still works). I guess it's a goofy tech word now.

show 1 reply
AshleysBraintoday at 9:07 AM

Is this not a good example of how generative AI does copyright laundering? Suppose the image was AI generated and it did a bad copy of the source image that was in the training data, which seems likely with such a widely disseminated image. When using generative AI to produce anything else, how do you know it's not just doing a bad quality copy-paste of someone else's work? Are you going to scour the internet for the source? Will the AI tell you? What if code generation is copy-pasting GPL-licensed code in to your proprietary codebase? The likelihood of this, the lack of a way to easily know it's happening, and the risks it causes, seems to me to be being overlooked amidst all the AI hype. And generative AI is a lot less impressive if it often works as a bad quality copy paste tool rather than the galaxy brain intelligence some like to portray it as.

show 3 replies
nicboutoday at 10:12 AM

> Is there even a goal here beyond "generating content"?

This is the part that hurts. It's all so pointless, so perfunctory. A web of incentives run amok. Systems too slick to stop moving. Is this what living inside the paperclip maximizer feels like?

Words we didn't write, thoughts we didn't have, for engagement, for a media presence, for an audience you can peddle yourself to when your bullshit job gets automated. All of that technology, all those resources, and we use it to drown humanity in noise.

show 2 replies
crossroadsguytoday at 7:54 AM

Something tangential..

> people started tagging me on Bluesky and Hacker News

Never knew tagging was a thing on Hacker News. Is it a special feature for crème de crème users?

show 1 reply
bob1029today at 9:07 AM

This is why we don't use diffusion style models for diagrams or anything containing detailed typography.

An LLM driving mermaid with text tokens will produce infinitely more accurate diagrams than something operating in raster space.

A lot of the hate being generated seems due to really poor application of the technology. Not evil intent or incapable technology. Bad engineering. Not understanding when to use png vs jpeg. That kind of thing.

show 1 reply
My_Nametoday at 12:20 PM

Of course, if you use AI, it's very hard to know the sources used for training that went into the output you just got.

ezsttoday at 7:17 AM

Waiting for the LLM evangelists to tell us that their box of weights of choice did that on purpose to create engagement as a sentient entity understanding the nature of tech marketing, or that OP should try again with quatuor 4.9-extended (that really ships AGI with the $5k monthly subscription addon) because it refactored their pet project last week into a compilable state, after only boiling 3 oceans.

show 4 replies
bulbartoday at 8:38 AM

Good example of the fact that LLMs, as its core, are lossy compression algorithm that are able to fill in the gaps very cleverly.

chromeheartstoday at 7:01 AM

Billions must morge

show 1 reply
aftergibsontoday at 7:59 AM

Archive.org shows this went live last September: https://web.archive.org/web/20250108142456/https://learn.mic...

It took ~5 months for anyone to notice and fix something that is obviously wrong at a glance.

How many people saw that page, skimmed it, and thought “good enough”? That feels like a pretty honest reflection of the state of knowledge work right now. Everyone is running at a velocity where quality, craft and care are optional luxuries. Authors don’t have time to write properly, reviewers don’t have time to review properly, and readers don’t have time to read properly.

So we end up shipping documentation that nobody really reads and nobody really owns. The process says “published”, so it’s done.

AI didn’t create this, it just dramatically lowers the cost of producing text and images that look plausible enough to pass a quick skim. If anything it makes the underlying problem worse: more content, less attention, less understanding.

It was already possible to cargo-cult GitFlow by copying the diagram without reading the context. Now we’re cargo-culting diagrams that were generated without understanding in the first place.

If the reality is that we’re too busy to write, review, or read properly, what is the actual function of this documentation beyond being checkbox output?

show 4 replies
zahlmantoday at 7:41 AM

I'm glad I actually checked TFA before asking here if "morging" referred to some actual technical concept I hadn't previously heard of.

show 1 reply
rambambramtoday at 10:21 AM

Microsoft is only doing something about this now because there's enough evidence for a lawsuit. I don't know about the US, but the author seems to be from The Netherlands. Correct me if I'm wrong (and I don't know the exact legal name for it now), but there's something like a right to not get 'distortion or mutilation of intellectual property'.

Microsoft just spits in this creator's face by mutilating his creation in a bad way.

jacquesmtoday at 10:01 AM

I wonder how far the balance will have to tip before the general public realizes the danger. Humanity's combined culture, for better or worse, up to 2021 or so was captured in a very large but still ultimately finite stream of bits. And now we're diluting those bits at an ever greater speed. The tipping point where there are more generated than handcrafted bits is rapidly approaching and obviously it won't stop there. A few more years and the genuine article is going to be a rarity.

eurekintoday at 9:36 AM

It's funny how big of an impact individual developers can have with such seemingly simple publications. At the time of the article with that diagram release, I was changing jobs and I distinctly remember, that the diagram was extensively discussed and compared to company standards, at both the old and the new place.

ifh-hntoday at 12:30 PM

I had to look up what "morged" meant, it's either morph and merge or a youtuber. I'm going with the first.

I can't find a link to the learn page so can only see what's on the article. Is this a real big deal? Genuine question, driveby downvote if you must.

Even if this was a product of AI surely it's just a case of fessing up and citing the source? Yeah it doesn't look good for MS but it's hardly the end of the world considering how much shit AI has ripped off... I might be missing something.

show 2 replies
KronisLVtoday at 9:04 AM

> take someone's carefully crafted work, run it through a machine to wash off the fingerprints, and ship it as your own.

I don’t even care about AI or not here. That’s like copying someone’s work, badly, and either not understanding or not giving a shit that it’s wrong? I’m not sure which of those two is worse.

alex_suzukitoday at 6:45 AM

From TFA:

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

Most content will be less known and the ensloppified version more obfuscated... the author is lucky to have such an obvious association. Curious to see if MSFT will react in any meaningful way to this.

Edit: typo

show 1 reply
AndroTuxtoday at 7:26 AM

“It was careless, blatantly amateuristic, and lacking any ambition, to put it gently. Microsoft unworthy.”

Seems to be perfectly on brand for Microsoft, I don’t see the issue.

show 1 reply
zkmontoday at 6:50 AM

That old beatiful git branching model got printed into the minds of many. Any other visual is not going to replace it. The flood of 'plastic' incarnations of everything is abominable. Escape to jungles!!

show 1 reply
jrontoday at 7:37 AM

Morged > Oneshotted

beeflettoday at 7:56 AM

Developer BRUTALLY FRAME-MORGED by Microsoft AI

bayindirhtoday at 6:43 AM

Sorry but, isn't this textbook Microsoft? Aside being more blatant, careless and on the nose; what's different than past Microsoft?

These people distilled the knowledge of AppGet's developer to create the same thing from scratch and "Thank(!)" him for being that naive.

Edit: Yes, after experiencing Microsoft for 20+ odd years, I don't trust them.

kgeisttoday at 8:23 AM

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

"Don't attribute to malice what can be adequately explained by stupidity". I bet someone just typed into ChatGPT/Copilot, "generate a Git flow diagram," and it searched the web, found your image, and decided to recreate it by using as a reference (there's probably something in the reasoning traces like, "I found a relevant image, but the user specifically asked me to generate one, so I'll create my own version now.") The person creating the documentation didn't bother to check...

Or maybe the image was already in the weights.

show 1 reply
kshri24today at 8:27 AM

I can already tell this is probably some AI Microslop fuck up without even clicking on the article.

EDIT: Worse than I thought! Who in their right mind uses AI to generate technical diagrams? SMDH!

usefulpostertoday at 6:50 AM

Hey, it's just like the Gas Town diagrams.

https://news.ycombinator.com/item?id=46746045

show 1 reply
ftchdtoday at 10:28 AM

is this the HN version of "mogged my frame"?

dotditoday at 7:21 AM

I guess this image generation feature should never have been continvoucly morged back into their slop machine

bschwindHNtoday at 8:50 AM

> The AI rip-off was not just ugly. It was careless, blatantly amateuristic, and lacking any ambition, to put it gently.

That pretty much describes Microsoft and all they do. Money can't buy taste.

He was right:

https://www.youtube.com/watch?v=3KdlJlHAAbQ

zombottoday at 10:24 AM

Continvoucly! Well morged.

bitwizetoday at 6:44 AM

I love it when the LLM said "it's morgin' time" and proceeded to morg all over the place.

show 1 reply
whirlwintoday at 7:06 AM

The new Head of Quality in Microsoft has not started working there yet, so it's business as usual at MS... And now with AI slop on top

Ref: https://www.reddit.com/r/technology/comments/1r1tphx/microso...

show 1 reply
shaky-carrouseltoday at 8:57 AM

> The AI rip-off was not just ugly. It was careless, blatantly amateuristic, and lacking any ambition, to put it gently. Microsoft unworthy.

LOL, I disagree. It's very on brand for Microslop.

isoprophlextoday at 7:35 AM

> The AI rip-off was not just ugly. It was careless, blatantly amateuristic, and lacking any ambition, to put it gently. Microsoft unworthy.

lmao where has the author been?! this has been the quintessential Microsoft experience since windows 7, or maybe even XP...

WesolyKubeczektoday at 7:49 AM

I propose to adopt the word „morge”, a verb meaning „use an LLM to generate content that badly but recognizably plagiarizes some other known/famous work”.

A noun describing such piece of slop could be „morgery”.

show 1 reply
laroditoday at 8:04 AM

Everything you publish now on will be stolen and reused one way or another.

zephentoday at 7:10 AM

On the one hand, I feel for people who have their creations ripped off.

On the other hand, it makes sense for Microsoft to rip this off, as part of the continuing enshittification of, well, everything.

Having been subjected to GitFlow at a previous employer, after having already done git for years and version control for decades, I can say that GitFlow is... not good.

And, I'm not the only one who feels this way.

https://news.ycombinator.com/item?id=9744059

🔗 View 7 more comments