Live data from Hacker News

Letter To A Young Programmer Considering A Startup

al3x.net

21–30 of 162 posts

Re: Letter To A Young Programmer Considering A Startup

#21
Don't start a company because you like coding, Aza Raskin summed it up nicely for designers but same hold trues for programmers (http://www.azarask.in/blog/post/psychological-pitfalls-and-l...)

Working for a startup has been a good source of learning new skills for me but as the author notes can be hazardous to the rest of your life...

Re: Letter To A Young Programmer Considering A Startup

#22

"There are so many ways to make a dent in the world", he says, but fails to suggest any. So what if the startup thing isn't all it's cracked up to be? It's still better than the alternative. What else are you going to do? Go waste your time in a big corporation learning how to withstand endless, meaningless tedium? If you're young you can probably afford to take some risk, so go take some risk! Take a shot at accompl…

There are plenty of small to medium sized business where you get to learn and have an impact. I tend to favor those - I have the autonomy to contribute without the overhead of 6 different managers.

Re: Letter To A Young Programmer Considering A Startup

#23

"There are so many ways to make a dent in the world", he says, but fails to suggest any. So what if the startup thing isn't all it's cracked up to be? It's still better than the alternative. What else are you going to do? Go waste your time in a big corporation learning how to withstand endless, meaningless tedium? If you're young you can probably afford to take some risk, so go take some risk! Take a shot at accompl…

Honestly, my observation is that there's nothing out there that "gives you" that opportunity. You have to make it. Fight for it. Steal time if you must. The idealized university-like company that makes you more productive as a part of it than you would be with 100% freedom over your time is, at this point, an extreme rarity. The basic-research labs have been pretty much shut down.

The problem with shitty startups is that they mislead people into believing that they're opening so many doors that it's worth letting the networking and independent skill building (each of which should get 10 hours per week; ideally that's out-of-work but do it at the expense of your day job if necessary-- fire up a MOOC during a workday lull; diversify) go to slack. Then, they pass four years of 60-hour weeks only to find that the executive-level or research (everyone wants to be an executive or in R&D; either controlling others or free from control) roles promised them were given to new hires or don't exist, and they realize they've wasted 4 years of their lives.

The lesson isn't "never work for startups" because there are great startups and (obviously) awful big-company jobs. It's "don't believe the hype and let your networking and independent learning go to hell". You only go all-in as a founder, not as some subordinate employee. The latter is just stupid; but you see it all the time.

Re: Letter To A Young Programmer Considering A Startup

#24

one point al3x didn't talk to: not all startups will teach you to be an awesome engineer. If a startup is really hiring the best of best, a less experienced programmer is not likely to make the cut. Ever look at your code from 6 months, a year, 5 years ago? and how bad it is? Many tech startups don't have time for that, the quality of your work can make or break a startup. Elite startups want "ex-googlers". So if you…

Great point. A good rule of thumb in jobs is that if you are the undisputed top , make sure that you are being compensated very, very well. Because you just sold out. It is quite hard to reach new levels of expertise without explicit, task-related mentoring, and if you're trading off that kind of growth, do it explicitly. Back when I was a manager, I used to find it somewhat depressing to interview people who had gon…

Certainly, they knew more "things" but had failed to grow in either scope or depth.

It's really easy to let career development and general-purpose learning go to slack when you believe this thing you're spending 80 hours per week on is going to make you rich and change the world-- and when you're surrounded by people who (equally irrationally) believe the exact same thing.

Re: Letter To A Young Programmer Considering A Startup

#25
post #20

Startups have become something of a career path or lifestyle. It has developed into a scene, with its own media coverage and drama. I see a lot of clueless college students wanting to "do startups" as if it were any old job. My perspective is this: Found or join a startup if have a specific product/service you want to build at a large scale. You'll earn your wealth through the equivalent amount of pain ( http://www.p…

But coming to SF and floundering around is no better than aimlessly moving to LA to become a movie star. Not to be nit-picky but getting start-up experience isn't quite the same as going to casting calls while working at Olive Garden to make ends meet.

What about when you work at a no-name software shop to make ends meet while you pitch to VCs to get your own startup off the ground?

The analogy may be more apt than it first seems! ;)

Re: Letter To A Young Programmer Considering A Startup

#26
You see the same problems in students going to film school because they like to see themselves as a director. You see the same problems in big studios making blockbusters for money.

To be Primer, you have to have a specific, burning idea. To be Fassbinder, you need to have something to say (and be a genius).

Else, you can only aspire to be Cars 2 or The Phantom Menace.

Re: Letter To A Young Programmer Considering A Startup

#27
And this is why I stopped playing that particular game and started playing a very different, but no less systematized and traditional game: being a consultant software developer with clients that pay per project or per hour, rather than in four-year equity vesting cycles.

Re: Letter To A Young Programmer Considering A Startup

#28
Business influence, autonomy, responsibility, variety, opportunity, risk, unclear solutions to open problems : things a small new startup are likely to offer to a 2[0-9] year old and a large business is less likely to.

The question is, do your personality and abilities suit a startup environment? Or is one more fitted to a structured environment? Maybe a short internship would tell.

If someone inexperienced says they want to do a startup, my advice would be to join a business with 40 to 80 employees in a market that interests you, learn how to tell who are the productive people in sales, marketing, operations and development and start a business with a couple of them. Work out which ones are hard working, effective and entrepreneurial and want to begin a business. Knowing who is excellent in areas you are weak in is a critical skill to learn (and I find extremely hard to judge unless working fairly closely with them). Many many businesses don't know who the real key employees are, or are under-valuing/under-appreciating them.

I had opportunity to join the most effective dev and marketer in a business I was working in when 24 and I didn't jump on the opportunity so I missed out (stupid me). I created a similar opportunity many years later, and it is working out very well (although rough for a couple of years).

Re: Letter To A Young Programmer Considering A Startup

#30

one point al3x didn't talk to: not all startups will teach you to be an awesome engineer. If a startup is really hiring the best of best, a less experienced programmer is not likely to make the cut. Ever look at your code from 6 months, a year, 5 years ago? and how bad it is? Many tech startups don't have time for that, the quality of your work can make or break a startup. Elite startups want "ex-googlers". So if you…

Great point. A good rule of thumb in jobs is that if you are the undisputed top , make sure that you are being compensated very, very well. Because you just sold out. It is quite hard to reach new levels of expertise without explicit, task-related mentoring, and if you're trading off that kind of growth, do it explicitly. Back when I was a manager, I used to find it somewhat depressing to interview people who had gon…

that first sentance is an amazing way to frame salary negotiation, thank you!
Post reply on HN