Please let morged become a thing.
Satya yelled "it's morgin' time" and then morged all over the place.
If you've got the tiന്ന, we've got the morge.
15 years later, Microsoft morged my diagram
61–70 of 427 posts
Re: 15 years later, Microsoft morged my diagram
#62Microsoft 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 f…
Seems like this is going to be the year of AI slop being released everywhere by Microsoft. Just wish they'd put as much effort into a post morten for this one as they're doing for a diagram on a blog post https://github.com/microsoft/onnxruntime/issues/27263#issuec...
Re: 15 years later, Microsoft morged my diagram
#63Earlier quoted context omitted.
Maybe you're missing the reference to the Morbius movie joke, which sounds surprisingly fitting. It's not like older HNers never made funny references. Edit: Apparently you didn't.
The commenter you're responding to a) independently made the exact same reference; b) has a username like that of Jared Leto's other Disney tentpole flop role...
Well spotted, I guess they're pushing for HN's redditification then.
Re: 15 years later, Microsoft morged my diagram
#64They've taken it down now and replaced with an arguably even less helpful diagram, but the original is archived: https://archive.is/twft6
Wow it’s even worse than I thought. I thought that convictungly morhing would be the only problem. The nonsense and inconsistent arrowheads, the missing annotations, the missing bubbles. The “tirm” axis… That this was ever published shows a supreme lack of care.
The turn axis is great! Not only have they invented their own letter (it's not r, or n, or m, but one more than m!), it points the wrong way.
Re: 15 years later, Microsoft morged my diagram
#65A somewhat contrarian perspective is that this diagram is so simple and widely used and has been reproduced (ie redrawn) so many times that is very easy to assume this does not have a single origin and that its public domain.
That's pretty hard to reconcile with OP's claim:
> 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.
If you mean that the Microsoft publisher shouldn't be faulted for assuming it would be okay to reproduce the diagram... then said publisher should have actually reproduced the diagram instead of morging it.
Re: 15 years later, Microsoft morged my diagram
#66Microsoft 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 f…
Microsoft seems to have thrown quality assurance overboard completely. Vibe generate everything, throw it at a wall, see what sticks. Tech bros are so afraid of regulation they even drop regulation inside their own companies. (just kidding)
It's not just throwing QA out, they are actively striving for lower quality because it saves money.
They're chasing that sweet cost reduction by making cheap steel without regard for what it'll be used for in the future.
Re: 15 years later, Microsoft morged my diagram
#67Microsoft 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 f…
Yeah, isn't this why we're told everything "moves so much slower at a bigco" than at a startup?
Re: 15 years later, Microsoft morged my diagram
#68Microsoft 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 f…
> In either case -- no review process, or a failed review process -- the failure is definitionally systemic.
Ortho and grammar errors should have been corrected, but do you really expect a review process to identify that a diagram is a copy from another one some rando already published on the internet years ago?
Re: 15 years later, Microsoft morged my diagram
#69I'm glad I actually checked TFA before asking here if "morging" referred to some actual technical concept I hadn't previously heard of.
If we are here, lets at least coin it for something relevant!
Re: 15 years later, Microsoft morged my diagram
#70I 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”.