Live data from Hacker News

15 years later, Microsoft morged my diagram

nvie.com

271–280 of 427 posts

Re: 15 years later, Microsoft morged my diagram

#271
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…

If what they described is "trunk based development", then "git flow" is just "trunk based development where the trunk is called develop and there's a branch which always has the latest release". Is that it?

Re: 15 years later, Microsoft morged my diagram

#272
https://en.wiktionary.org/wiki/morg

Morg doesn't seem to be a word in English (though it is in Irish!), but it sounds like it should be.

This is one aspect of AI I will miss, if we ever figure out how to make it go away. The delightful chaos. It invented a word here, without even meaning to.

For example, I vibe coded a QWOP clone the other day, and instead of working human legs, it gave me helicopter legs. You can't walk, but if you mash the keyboard, your legs function as a helicopter and you can fly through the sky.

That obviously wasn't intentional! But it was wonderful. I fear that in a few years, AI will be good enough to give me legs that don't fly like a helicopter. I think we will have lost something special at that point.

When I program manually, I am very good at programming bugs. If I'm trying to make something reliable, that's terrible. But if I'm trying to make a computer do something nobody even realized it can do... making it do things you weren't expecting is the only reliable way to do that.

So I've been working on a way to reintroduce bugs mechanically, by mutating the AST. The fundamental idea is sound -- most of my bugs come from "stuff I obviously meant to type, but didn't" -- but it needs a bit more work. Right now it just produces nonsense even I wouldn't come up with :)

I currently have "mess up the file". The next 2 phases would be "in a way so that it still compiles", and "in a way so that it doesn't (immediately) crash at runtime", (since the whole point is "it still runs, but it does something weird!"). More research needed :)

Re: 15 years later, Microsoft morged my diagram

#273
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…

I am working with main/master for years now, and there's one problem you don't have with develop: Whenever you merge something into master, it kind of blocks the next release until its (non-continuous) QA is done. If your changes are somewhat independent, you can cherry-pick them from develop into master in an arbitrary order and call that a release whenever you want to.

What's the difference between what you describe, and continuously merging things into main and cutting releases from a branch called stable?

Re: 15 years later, Microsoft morged my diagram

#275
post #272

https://en.wiktionary.org/wiki/morg Morg doesn't seem to be a word in English (though it is in Irish!), but it sounds like it should be. This is one aspect of AI I will miss, if we ever figure out how to make it go away. The delightful chaos. It invented a word here, without even meaning to. For example, I vibe coded a QWOP clone the other day, and instead of working human legs, it gave me helicopter legs. You can't…

I appreciate humorous outcomes but not when I’m trying to solve concrete task. I’m sure an LLM that is designed to introduce a little chaos is not hard to make. All I know is I won’t miss the weird and incorrect output if they ever get more consistent.

Re: 15 years later, Microsoft morged my diagram

#276
post #190

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

Well Bill Gates declared it 20 years ago : "Content is king", so here we are. "Content" everywhere, and not just the Internet - go to anny tourist hotspot, there is a ratio of 5:1 of idiot influencers all stretching their faces in front of the same landmarks. Your utility company now produces "content" for some reason. Every lazy Tom, Dick and Joe produce "content" instead of doing their trade. Apps that summarise your books so you can "read" them on your commute. To the ghouls who are driving the "content" economy, everything is "content". They don't really understand either long form or novels, or music or anything creative. To them it's all just content, to be bought, sold and consumed by the pound.

Re: 15 years later, Microsoft morged my diagram

#277

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

HN is a Serious Place. We're here to make money. Please leave your jokes at home.

[deleted]

Re: 15 years later, Microsoft morged my diagram

#278
post #272

https://en.wiktionary.org/wiki/morg Morg doesn't seem to be a word in English (though it is in Irish!), but it sounds like it should be. This is one aspect of AI I will miss, if we ever figure out how to make it go away. The delightful chaos. It invented a word here, without even meaning to. For example, I vibe coded a QWOP clone the other day, and instead of working human legs, it gave me helicopter legs. You can't…

I appreciate humorous outcomes but not when I’m trying to solve concrete task. I’m sure an LLM that is designed to introduce a little chaos is not hard to make. All I know is I won’t miss the weird and incorrect output if they ever get more consistent.

The real question is can we get consistency without mode collapse? Are they orthogonal, or necessarily opposed?

Or to put it more bluntly.. can we get correctness without cringe ;)

I think it could be done, to a degree, with current systems, but it would be more expensive. You'd increase the temperature, and then you'd do more runs. And you could do that iteratively... re-generate each paragraph a few times, take the best of N. So you end up with interesting output, which still meets some threshold of quality.

Actually that doesn't sound too hard to slap together right now...

Re: 15 years later, Microsoft morged my diagram

#279
post #272

https://en.wiktionary.org/wiki/morg Morg doesn't seem to be a word in English (though it is in Irish!), but it sounds like it should be. This is one aspect of AI I will miss, if we ever figure out how to make it go away. The delightful chaos. It invented a word here, without even meaning to. For example, I vibe coded a QWOP clone the other day, and instead of working human legs, it gave me helicopter legs. You can't…

Nothing delightful of funny here mate. Imagine being a junior just starting out reading that shitty piece of content, trying to make sense of it all?

Re: 15 years later, Microsoft morged my diagram

#280

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

> "everything is moving very fast" Then slow down. With this objective lack or control, sooner or later your LLM experiments in production will drive into a wall instead of hitting a little pothole like this diagram.

"Driving into a wall" is still a positive outcome. It's just as likely to drive into a crowd.
Post reply on HN