3 ms·
You could describe YCombinator as a means for rectifying this imbalance. I think the author glances over too lightly the idea of good developers working for eq
by jimbokun 18y ago
You could describe YCombinator as a means for rectifying this imbalance.
I think the author glances over too lightly the idea of good developers working for equity. A core part of the YC philosophy is that it is much easier to take a great hacker and teach them the business skills they need to succeed, than to take someone with business skills and make them a great hacker. (I'm basing this on something from one of pg's essays, sorry, can't remember which one at the moment.)
Based on the kind of output that the average YC team puts out during the program, a 10x multiple over the average corporate programmer's output during the same time is a reasonable estimate. Part of this is because, even if you have a corporate programmer capable of 10x more productivity than his peers, the processes surrounding him likely make it impossible for him to get that much work deployed in that amount of time.
And I think that is another important thing to consider. Corporations do not pay developers who are 10x as productive 10x as much because the way they develop and deploy software makes it impossible for them to realize a 10x productivity improvement, in any case.
EDIT: Just thought of a possible rebuttal I would like to address. You might compare this to the sports star, and point out that the star is not taking on the risk associated with getting paid in equity. However, an athlete's career is also an extremely high risk endeavor. Just as most startups fail, obviously the vast majority of athletes fail to make a lucrative career out of their athletic prowess. I would venture that the selectivity for an athlete looking for a lucrative contract is much higher than the selectivity for a hacker managing to start a lucrative business.
- umjames 18y agoI think it was another pg essay (possibly http://www.paulgraham.com/opensource.html http://www.paulgraham.com/opensource.html) which suggests that workplaces have office hours because they can't accurately measure an employee's productivity. So they aren't likely to know where the productivity is really coming from anyway. Even if they know you're 10x as productive as the other developers, they may not reward you so as not to make the other developers jealous or resentful.