Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

15 years later, Microsoft morged my diagram

nvie.com

Post reply on HN
Print view View original

191–200 of 427 posts

Re: 15 years later, Microsoft morged my diagram

#191

Post by sshagent »

cwal37 wrote: post #10

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 incentiv…

totally. I'm really getting behind the slight replacement of TL;DR to AI;DR If you can't be bothered to read your own AI slop, then I'm not reading it either.

Re: 15 years later, Microsoft morged my diagram

#193

Post by ozim »

wiseowise wrote: post #170
ozim wrote: post #36

Earlier quoted context omitted.

There are people who write genuinely interesting stuff there as well. I use block option there quite a lot. That cleans up my experience rather well.

Can to share some of them? Genuinely curious.

I guess people one would follow on other platforms, plus bunch others posting in my native language.

Daniel Stenberg Jason Fried David Heinemeier Hansson Nick Chapsas Laurie Kirk Brian Krebs

Re: 15 years later, Microsoft morged my diagram

#195

Post by rambambram »

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.

Re: 15 years later, Microsoft morged my diagram

#196

Post by nananana9 »

cjs_ac wrote: post #178
hansmayer wrote: post #105

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

The weakest point in any computer system is the bag of meat operating the thing.

Can we stop calling humans "bags of meat"?

Re: 15 years later, Microsoft morged my diagram

#198

Post by benhurmarcel »

cwal37 wrote: post #10

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 incentiv…

> these people clearly aren't reading anything they're posting

I'm surprised they are able to care so little. Somebody actually published this and didn't care enough to even skim through it.

Re: 15 years later, Microsoft morged my diagram

#200

Post by iainmerrick »

m12k wrote: post #137

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 branc…

You’re right. I think what you’re describing is “trunk based development” and it’s much better.

Maybe I’m overly cynical but I think git-flow was popular largely because of the catchy name and catchy diagram. When you point out that it has some redundant or counter-productive parts, people push back: “it’s a successful model! It’s standard! What makes you think you can do better?”

There’s a nice write-up of the trunk-based style at https://trunkbaseddevelopment.com/ that you can point to as something better.

Post reply on HN