Live data from Hacker News

YC is a cult

danielharan.com

101–110 of 159 posts

Re: YC is a cult

#101
post #91

Earlier quoted context omitted.

As far as I can tell, how hard people work has little correlation with whether they have follower-type personalities. It does, however, have quite a high correlation with working on a startup. So my guess is the cause is that they're working on a startup.

So do you condone working such long hours that founders are routinely sleep deprived?

Quit trolling. Clearly it's the founder's decision how many hours to work, not PG's.

Re: YC is a cult

#102
post #74

Actually there's a fundamental incompatibility between cults and startups. Cult followers tend to be people who want someone to tell them what to do. There are a lot of people like that, but they're the opposite of the kind of people who make good startup founders. What you want in a startup founder is the sort of tenacious independent mindedness that makes you start a new search engine in 1998, when everyone else th…

So, what's up with these insane hours? You've written about the need for working long hours, but aren't Michael Parkatti and Mike Marrone taking it a bit too far?

I'd like to point out that I've never been entirely the type to put in insane work hours. To be fair, I've probably always worked more than the average person, but my particular peak efficiency (as I've been able to see while using RescueTime) comes when I work for bursts and then rest.

All of that being said, ever since I've been a founder (and especially during YC), I've noticed my work time shooting off the charts compared to how I used to work for other companies. I know why this is for me: it's simply because I know that every minute I'm not working is a minute that I'm subtracting from the company's success timeline. People talk about compressing your career into the span of 4 years as a founder, and yeah that's really what's going on. The reason is because if you don't work on your startup, there literally is nobody else that will. And for me, it feels like I'm costing myself money when I'm not working, and that takes a while for people like me to figure out how to balance. I have found that it gets easier after you've reached a more stable 1.0 of your product, but it's always a challenge.

I must say, though, that the idea that YC is a cult is pretty ridiculous.

Re: YC is a cult

#103
post #91

Earlier quoted context omitted.

As far as I can tell, how hard people work has little correlation with whether they have follower-type personalities. It does, however, have quite a high correlation with working on a startup. So my guess is the cause is that they're working on a startup.

So do you condone working such long hours that founders are routinely sleep deprived?

"Even during Viaweb I still slept 8 hours a night (roughly 3-11). The most productive people rarely have more than 6 hours or so of really concentrated work per day, except in emergencies. If you can ensure you get that every day, you don't need to economize on sleep..." -- by pg 358 days ago

http://news.ycombinator.com/item?id=39778

Re: YC is a cult

#104
post #33

It's sad to see this trollish content rising to the top of news.yc.

Sorry, but all your comment does is pretty much confirm the article. Dismissing criticism as "trolling" is exactly what a cult member would do. Even invalid criticism warrants a proper rebuttal, if at the least to educate those leveling the criticism as to their errors. The fact that it has risen to top stop this morning only serves to illustrate that there are many things about the YC process that people don't parti…

I think you may be mistaken about which Paul you're responding to. http://news.ycombinator.com/user?id=paul

Re: YC is a cult

#105
post #33

It's sad to see this trollish content rising to the top of news.yc.

I think the only reason it hasn't been killed is that "silencing critical voices" would be added to the list of offenses. That doesn't bother me at all though. That's just not a good reason to avoid killing a weak troll post.

Re: YC is a cult

#106
post #104

Earlier quoted context omitted.

Sorry, but all your comment does is pretty much confirm the article. Dismissing criticism as "trolling" is exactly what a cult member would do. Even invalid criticism warrants a proper rebuttal, if at the least to educate those leveling the criticism as to their errors. The fact that it has risen to top stop this morning only serves to illustrate that there are many things about the YC process that people don't parti…

I think you may be mistaken about which Paul you're responding to. http://news.ycombinator.com/user?id=paul

I know it's "gmail Paul", but my comment still stands.

I thought your comment was a more appropriate response, to be honest.

Re: YC is a cult

#107

Earlier quoted context omitted.

Except, in Apollo people died/can die. That is a rather silly criterion. All engineers build things that can kill people if they go wrong. That's what engineers do. You think that social software can't be used to kill people? Do you know the number of people (mostly women) who are murdered each year by stalkers, most of whom are former lovers or spouses? Do you want to bet that none of those stalkers have used, say,…

Apollo engineers make a design mistake, it kills people. If you don't like that because it doesn't effect enough people (Sorry I didn't realize that since Facebook serves 100 million people it is more of a feat than going to the moon) lets talk about Boeing. Boeing makes a design mistake, hundreds of people die. That has happened and will continue to happen. Now you compare that to Facebook - if Facebook or Google go…

I think the test of the importance of your work is not how much people will be hurt if you screw up, but how much people's lives are improved if you succeed. Some of the most important work is done by people working quietly on mundane problems. Judged by the standard of how much it contributes to people's well-being, Google probably does more for the world than the Apollo missions did.

Re: YC is a cult

#108
post #30

Earlier quoted context omitted.

Where did I compare them? My comment just pointed out that the definition of a cult used in the blog post falls down badly when applied to famous successful projects (which we can presumably agree were not cults), and is therefore either being misused or broken.

He's using the accepted psychological definition of a cult. The reference is right there in the post.

Hardly. Did you try following the link in the post? The link text says "textbook definition of a cult," but it's just a link to the Wikipedia article. This list is one of several that appear in the article, and judging from the multiple citations it is an amalgam created from several different sources.

Re: YC is a cult

#109
post #91

Earlier quoted context omitted.

As far as I can tell, how hard people work has little correlation with whether they have follower-type personalities. It does, however, have quite a high correlation with working on a startup. So my guess is the cause is that they're working on a startup.

So do you condone working such long hours that founders are routinely sleep deprived?

If you're going to troll, I want disclosure. How many times have you applied to YC and been rejected?

Re: YC is a cult

#110

Earlier quoted context omitted.

Except, in Apollo people died/can die. That is a rather silly criterion. All engineers build things that can kill people if they go wrong. That's what engineers do. You think that social software can't be used to kill people? Do you know the number of people (mostly women) who are murdered each year by stalkers, most of whom are former lovers or spouses? Do you want to bet that none of those stalkers have used, say,…

Apollo engineers make a design mistake, it kills people. If you don't like that because it doesn't effect enough people (Sorry I didn't realize that since Facebook serves 100 million people it is more of a feat than going to the moon) lets talk about Boeing. Boeing makes a design mistake, hundreds of people die. That has happened and will continue to happen. Now you compare that to Facebook - if Facebook or Google go…

wtf does that have to do with anything.

I have no idea. This whole conversation seems like a big tangent, and perhaps I'm having a bit too much fun following it off into infinity. Shame on me.

Anyway:

Yes, Boeing has a more difficult task than many startup founders. Of course, there are also more engineers at Boeing, and they've been working on the problem for a much longer time.

Yes, it would be possible for a Google or Facebook design error to get someone killed. Leaks of personal or financial information are potentially deadly. Bad information can be deadly.

No, I can't give you a specific example of a design error (as opposed to a user error) that killed a Google or Facebook user. That's partly because Google and Facebook engineers -- like Boeing engineers, and most engineers worthy of the name -- take their work seriously and don't make many consequential mistakes. But mostly it's because our standards are looser, and reasonably so: The internet is a twelve-year-old invention, and when planes were twelve years old people crashed and burned all the time. They were experimental, and nobody expected anything different.

Standards will change. We're hearing stories of users who followed a Google map off a road and are now suing Google for damages. Right now those stories serve as hilarious examples of lawsuit-happy, stupid people, but perhaps in fifty years middle-class people will expect digital maps to be perfectly accurate, just as today they expect to have clean water and lead-free plumbing, and to always be able to reach an operator by dialing 911 on their cell phone.

Finally, I don't think this sentence is correct, in general:

The fact that people misuse something doesn't make it the engineers fault.

The problem is that there's no bright, shining line. Your kitchen knife example is far to one side of the line: Because kitchen knives are a very well-established technology, most knife accidents are caused by people misusing the product. On the other side of the line is, say, food that's been sweetened with ethylene glycol. That's pretty obviously a design error. And in between is a huge grey area, in which most software falls. Is Boeing responsible when a confused pilot pulls the wrong lever and fails to lower the landing wheels? [1] Is the guy who built the buggy online spreadsheet responsible when the civil engineer uses it to design a bridge that falls down? Well, that's why we have courts -- and why your startup needs to have a lawyer.

[1] I do know that planes used to have a little wheel-shaped lever to guard against this very problem. Maybe they still do. I forget where I learned that -- was it from Donald Norman?

Post reply on HN