Fixed it for you :-)
I think salary IS a motivational factor in real life, as for many humans it is a yardstick of superiority compared to other humans (whether it is right or wrong is another matter).
Thinking about the brighter side of things I suppose that in the more than enough side of things you would be paid with happiness. That to be wealthy would be to have something you enjoy doing all of the time. Success however, would be measured in a currency that is more difficult to track, respect.
I have asked many people this and only two people have said yes to this. One was someone who already sold his startup so probably didn't have to work ever again. The other was someone who could have retired but he was afraid if he shut down his company his employees would struggle to find new jobs.
I'm torn between thinking of Hacker News as benevolent or delusional and self-righteous.
I get the benevolent vibes when I see comments like golergka's. I get the delusional, self-righteous vibes when I see founders and VCs comparing themselves to JP Morgan and JD Rockefeller, saying "Hey! Look! I'm just as important as those guys!" "Silicon Valley is important!"
That said, Silicon Valley may very well be an important part of history. But the self-centeredness makes me wary.
>I get the benevolent vibes when I see comments like golergka's
I think his comment is benevolent, not delusional.
But. There's a reason why certain people choose it. You can be less of a cog.
Thanks, but why? My comment works in completely capitalist self-interest way, even when you forget about all the joy of programming.
When I was a manager in big corp, here what was important for us. These things you will not gain in some start ups (and in some you will definitely learn):
- How to write and communicate functional, design, and QA specs
- How to properly setup unit, module, program, product, and system testing
- Understand security issues
And the funny thing is that startups which will help you to grown in areas above are anyway going to be ones which do offer market base salary.
But if you ask whether they give you more money because you are now in another relationship with them (consulting?), then absolutely, yes.
It's one thing to hire just a developer. It's another thing to hire a developer who knows first-hand what's it like to run a startup, what's important for management and what concerns do they have.
The best decision I made in my career was to ride the 2003 recession in a small catalog company that wrote its own code and wanted to grow. Since they were that small, I had responsibilities that had nothing to do with what people of my experience had to do in big companies. I was making stack and architectural decisions quickly. Since we didn't have an army of people, I had to do infrastructure, project proposals, requirements gathering, database administration, and decisions on stack changes. We just couldn't afford specialists. My pay was not exactly competitive, but when I left for a bigger company, I had major advantages over my coworkers, because I had such a breadth of experience compared to them, pigeonholed in roles that did a lot less, and never had to care about what was good for the business, just doing what the next guy in the totem pole said. Your idea of big bucks might be different from mine, but making over 300k in the Midwest sounds pretty good to me.
And it's not just my story: The rest of the people in that team are all doing extremely well. One is a senior architect in a cloud provider. Another is a pretty big conference speaker. The last one is the top technical gun in a consulting firm. All my friends that didn't take risks to go for better experience are doing far less interesting work, for far less money.
That said, a startup just makes it easier to get a job that teaches the right things. If all you end up doing is writing a web app in Rails, you might as well do that in a bigger place that pays better. It's not really about the office being cool, or thinking the company has a good chance at making it, but about finding ways to get a competitive advantage over other developers for the long haul.
Which is better depends entirely on the problem.
Do you have any advice for an undergrad trying to find his way in today's tech industry? You mentioned "competitive advantage" and learning the "right things" - could you elaborate on what you think that is today, especially for someone who'll be joining the workforce in about a year?
I've never heard that before but I realize now that it summarizes my motivations fairly succinctly