Live data from Hacker News

Fast

patrickcollison.com

131–140 of 306 posts

Re: Fast

#131

This reminds me of when I interviewed at Stripe, a few years back. It was a surreal experience. We were in a small conference room. I sat at the table on one side, Patrick and Edwin sat on the other side. They asked me questions, I answered them. It was a good discussion. Then there was a brief pause in the conversation. Suddenly, Patrick let off the most absurdly loud fart. I chuckled in surprise. Patrick and Edwin…

I’m going to guess dude just needed to let go and didn’t like that you laughed about it.

Maybe they just openly rip in the office and are used to it.

Maybe you didn’t get hired for totally unrelated reasons.

We’ll never know..

Re: Fast

#132
post #105
post #97

Earlier quoted context omitted.

For anyone looking for an in-depth post mortem of the Van Ness bus line, please read the report from the SF Civil Grand Jury here: https://civilgrandjury.sfgov.org/2020_2021/2021%20CGJ%20Repo...

Great report except it missed the most obvious recommendation: "decouple transit improvement from utilities projects"

The issue was that in this case they couldn’t — a lot of the BRT benefits came from creating a center lane, and that center lane was infeasible unless they did the utility project first.

Re: Fast

#133
post #71

Earlier quoted context omitted.

> I suspect it would still be pretty decent. A fun thought experiment, but I suspect they'd be bankrupt from the meritless lawsuits that come from being big, or in prison for not being able to follow laws they had to be big to lobby against. And even if not, the combined efforts of the scammers would probably evolve faster than two people could react.

Since we are in fun thought experiment mode, here’s another one I just had: what if we somehow could prevent companies from getting too big? Would we manage to keep a line where they all stay more or less in “pretty decent” territory?

By what metric, and how would it be different than antitrust enforcement?

E.g. a product that is clearly better can legally capture 100% market share. Only leveraging that market power is illegal.

I genuinely think a rule along the lines of "anything with 30%+ market share is scrutinized as having monopolistic network effect advantage" would have net positive outcomes on competition.

Re: Fast

#134

Major one missing: China built 5,000 miles of high speed rail in 6 years. In California, it's been 15 years and we have 0 miles complete. Also built numerous hospitals during pandemic in a couple weeks. Demolished and replaced a bridge in 43 hours: https://www.popularmechanics.com/technology/infrastructure/a... . General pattern of completing infrastructure projects at a blistering pace - and they work. Also landed a…

Look at YouTube for “Tofu Dreg” to see the results of rushed Chinese construction projects.

Re: Fast

#135
As another comment points out, what about "preparation" time?

I guess the timelines depend on when you start the clock.

Does anyone have a credible example of going fast, and where it really was a "zero to one" kind of process?

Re: Fast

#136

Having worked at a top 5 big tech company from college hire to a high level position, I have seen many factors that contribute to things being much slower than a startup. Some of them might be valid, but others are just the result of tragedy of large organisations (a big tech company is surprisingly similar to governments in terms of internal bureaucracy). * Large number of people and orgs willing and fighting to tak…

> a big tech company is surprisingly similar to governments in terms of internal bureaucracy Underrated point. It didn't really sink in for me until I saw the numbers with my own eyes. From a quick DDG search of publicly available info, here's [1] the numbers for FAANG headcount as of the end of 2022: - Meta: 86,000 - Apple: 164,000 - Amazon: 1,541,000 - Netflix: 12,800 - Google: 190,000 The numbers get a bit smaller…

Amazon and apple’s numbers are inflated by retail and warehouse staff significantly, who are effectively political non actors as far as this dynamic goes

Re: Fast

#137

Earlier quoted context omitted.

> a tremendous amount of time and effort was invested to retrofit it as such Great things require tremendous effort and even time.

That’s why git and JS don’t really belong on this list without a massive asterisk. It’s not like JS you use today is the same as the one that took “10 days”. Same goes for git.

Nevertheless, there's something amazing about being able to release the first version of something so world-changing so quickly.

Re: Fast

#138
Back in the early COVID days, an airplane with PPE landed in Prague. Responsible agency has been short handed so the staff of national budget oversight agency came to help in what was a prime example of violation of budgeting discipline and just unloaded the airplane.

I could not stop laughing about that for days. Other ministries were literally excusing themselves since "they were not allocated funds to deal with the pandemic and had other matters to addend to" and "doing job of another organization would be a violation of budget discipline". And then the literal guys responsible for auditing them for such violations just broke the rules and did the right and necessary thing.

In the end, it boils down to a simple rule. If you live in a society where rules outweight the public good and you can get into trouble for doing the right thing the "wrong way", progress grinds to a halt.

Re: Fast

#139
HTTP/2 was standardized in two years and 16 days.

That’s fast for standards :)

Re: Fast

#140
post #81

Earlier quoted context omitted.

Thats the story, but everyone who transited Van Ness during that time saw the same thing - very little work actually being done. The equipment just sat there idle most of the time. A more efficient process could have come in and finished the work, block by block in far less time if they actually, y'know, worked on it. People in construction tell me that it's because they're always waiting on the other guy to finish t…

There was a Grand Jury report analyzing the causes of the delay in the Van Ness project. While the unexpected conditions of the underground utilities is cited as the primary cause, it does touch on some project management aspects that you mention as opportunities for improvement: https://civilgrandjury.sfgov.org/2020_2021/2021%20CGJ%20Repo... Ironically, more planning and analysis at the beginning of the project (e.g…

I worked on that report! (Throwaway because, well, my real name is on the second page...)

The lack of meaningful technical planning was a big part of it, and so was the contract-awarding math, but I think the most striking - and generally applicable - behind-the-scenes stories were about what happens when trust breaks down at a human level. The city's internal back and forth on approving and then un-approving a subcontractor at the beginning meant that the GC was more likely to work to the letter of the contract when things went wrong later, instead of collaborating to solve problems. The one positive thing the city eventually did to get the project moving forward, according to all the information we got, was put someone with some amount of authority on the ground to talk to people.

Rereading the report now, all of these facts are in there, but I wish we'd found a way to stress this part more. You see the same thing in every industry, whether it's individuals or teams or companies working together - the best laid plans mean nothing unless the people involved are actually interested in tackling challenges as they come up. Culture eats strategy, and all that. A culture of writing a plan and then either strictly following it or throwing a fit when it can't be followed isn't a culture that can do great work.

Post reply on HN