1,408 karma · joined January 22, 2009
HN GOLD YOU SHOULD KNOW ABOUT: https://news.ycombinator.com/item?id=4247615 && https://news.ycombinator.com/item?id=2864156 && https://news.ycombinator.com/item?id=6041889
When you applied, did you have any reasonable expectation that you would actually be hired to work there, or was it just on a whim... like a lottery ticket?
I think the typical awesome engineer is just a shade too self-deprecating to even think it possible to get hired there.
Edit: "61.5 years is about the time it would take to rank in the top 3 results for the keyword 'google'."
Awesome, my grandkids are going to be so rich!
IMO, engineers have a tendency to calculate the value more precisely. :)
I mean, its very very hard to get it right the first time and hit one out of the park, so you have to try a million tiny things to find some things that stick. The trick is knowing when you're on to something and when you need to double-down. If you can't do that yourself, get outside people involved when you think you have something. If everyone walks away disinterested, you may not have anything yet... keep going.
The cure: both people must accept that the other person may actually have a good idea occasionally.
My intention wasn't to detract from his means of self-fulfillment, but perhaps that is what I have done.
Here's what I really mean by subsidizing, in context, and you can decide if it fits, or if I am suggesting something else...
If you buy into the idea that a developer, for example, can be 10x more productive than another, which I do (and I'm not one of the 10x guys at all), then you tend to think that those people should be paid a heap more than the average IT guy... but in fact, they are bound by the same corporate salary ranges as everyone else on the team... so you end up with the delta between the bottom guy and the most productive guy is at most 70K.
Therefore, thanks primarily to the top performers, our overall team performs well and everyone benefits similarly... but they really shouldn't benefit similarly since the amount of value creation is wildly different from developer to developer.
What I mean by my comment is that, as an entrepreneur, when I detect high marginal return on a given activity, I want to find ways of extracting more value from the situation for myself (profit seeking), rather than just getting a paycheck (profit taking).
All that value getting skimmed off and given to someone else is a lost opportunity, especially when you're working for someone else, as there are rarely ways to insert yourself at a higher point in the value chain.
I have often wondered why some companies (even mature ones) actively recruit entrepreneurially-minded folks. It just seems to me that they would create trouble for you once they realize you aren't acting like a market internally, and are only willing to pay labor-market rates (except in discreet circumstances).
Launched this last month: http://www.textmyoffice.com
Some other things still in the pipe.
As an entrepreneur, something about this statement bothers me... something about all the value I create getting skimmed off the top and taken away by someone else. Yeah, that's probably it.
But if you just want to do neat engineering work, then, sure, I get it.
Edit: One more thing... I think the end-game here is perfect competition, and I don't think that will be good for anyone.
3) Ideally, the name should describe what you do (or at least symbolize it), or be incredibly memorable.
It takes a while to come up with a good name. Spend the time necessary to pick the right one.
If you provide illiquid perks for participating in a review process, I don't see much wrong with that. If they were handing out cash, then yes, that is a grey area.
In general I don't think its wrong to ask for something in return for staking your reputation on a recommendation.