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

"We ran out of columns"

jimmyhmiller.github.io

Post reply on HN
Print view View original

581–588 of 588 posts

Re: "We ran out of columns"

#581

Post by CRConrad »

Suppafly wrote: post #549
oooyay wrote: post #316

Earlier quoted context omitted.

Before there was GitHub there was Sourceforge. Sourceforge supported several different protocols and git still won. Gits internals can be confusing at first, but once you understand them there's really nothing you can't do. Being distributed by design also helps.

To be fair, by the time git came around, sourceforge had been enshitifying itself for 10 years or so. Git would be popular without github, github just makes things easier.

> Git would be popular without github,

Yep.

> github just makes things easier.

Which is the transition between steps 1 and 2 of Embrace, Extend, Extinguish. Though the last step is nowadays perhaps unnecessary, depending on how you look at it: Having co-opted FOSS software like git, what you need to extinguish is not that itself, just any other way to use it than your own. The main example of step 2 was of course "Pull Requests".

Re: "We ran out of columns"

#582

Post by CRConrad »

celrod wrote: post #299
jimbokun wrote: post #241

Earlier quoted context omitted.

> Pixley agreed to all of that and then ignored all of it completely. Hahaha that's brilliant, and an important lesson for junior developers. Sometimes this is the best way forward. High risk of course. But the reward can be great.

I don't think you'd even necessarily need to ignore. Roll it out in phases. You aren't going to have to deliver the final finished solution all at once. Some elements are inevitably going to end up being de-prioritized, and pushed further into the future. Features that do end up having a lot of demand could remain a priority. I don't think this is even a case of "ask for forgiveness, not permission" (assuming you do…

> Some elements are inevitably going to end up being de-prioritized, and pushed further into the future. Features that do end up having a lot of demand could remain a priority.

Why, that sounds positively... Agile. In the genuine original sense.

Re: "We ran out of columns"

#583

Post by CRConrad »

cruffle_duffle wrote: post #232
kwhitefoot wrote: post #207

Earlier quoted context omitted.

Some of these stories sound a bit far fetched, especially those that involve Unix systems. RCS was released in 1982 and CVS in 1990 so Unix systems have had version control available for over forty years.

I can assure you they are true. Version control was still “controversial” in a lot of shops for quite some time. Plenty of places had the classic “v1, v2.3, v2_next_debug_cruffle_duffle” way of managing versions for a very, very long time. Well into the subversion era…

I know places that still do it that way. Not necessarily tiny places either.

Re: "We ran out of columns"

#584

Post by CRConrad »

trustno2 wrote: post #446
Aeolun wrote: post #335

Earlier quoted context omitted.

> He got furious when he was unable to call some journalist, cursed at me in front of the entire team and sent me a termination notice. Honestly does not sound like a very healthy person to work for anyway.

Does this seem like a healthy person to you? https://www.instagram.com/durov/

Depends on what you mean by "healthy". Physically, yes, sure looks so. But that's just one definition.

Re: "We ran out of columns"

#585

Post by CRConrad »

xp84 wrote: post #528
doublepg23 wrote: post #362

Earlier quoted context omitted.

Oldest boxes running are RHEL5 and Win Server 2008. I was trying to explain to the IT Director that both were released when I was in elementary school so I'd have to brush up on them.

cries in millennial

> cries in millennial

"Generation Z", I think.

Re: "We ran out of columns"

#586

Post by CRConrad »

PreInternet01 wrote: post #72
Vampiero wrote: post #57

Earlier quoted context omitted.

> Well, you move the type checks from the database to the app, effectively, which is not a new idea by any means (and a bad idea in many cases), but with JSON, it can actually work out nicely-ish, as long as there are no significant relationships between tables. That way you're throwing away 50% of the reason you use a relational database in the first place. Has it occurred to you that MongoDB exists? Also I don't un…

> Has it occurred to you that MongoDB exists? My original comment started with "but it feels "prior to the MongoDB-is-webscale memes"" So, care to take another guess? And, while we're here, does MongoDB run fully in-process these days? And/or allow easy pagination by ROWID?

> My original comment started with "but it feels "prior to the MongoDB-is-webscale memes""

Which feels off by six generations or so of memes. It feels prior to "memes" existing in the first place (at least this modern iteration, pics with captions in them; not Dawkins' original verion). I'd guess it is, ironically, chronologically closer to, well, your username here.

Re: "We ran out of columns"

#587

Post by CRConrad »

fragmede wrote: post #272
alt227 wrote: post #180

Earlier quoted context omitted.

Aside - the fact that cars dont include spares these days is infuriating. IMO its a classic example of real world enshittification

that's not enshittification! it sucks, yes, but when coined, the term referred to a platform extracting value from its users by degrading their experience, forcing them to upgrade to a premium plan. your car not having a spare isn't an example of that! https://en.wikipedia.org/wiki/Enshittification

Many of us grew up with cars having spare tyres as a matter of course. Now car manufacturers are extracting value from their customers by degrading our experience (of safety and expedience of repair), forcing us to pay extra for a spare tyre (if even available), or even upgrade to a better car.

Ordinary cars not having a spare tyre as standard equipment any more is a perfect example of enshittification.

Post reply on HN