Live data from Hacker News

Why you should join a big company first

geekwire.com

1–10 of 87 posts

Re: Why you should join a big company first

#2
I believe big companies are a good route for most devs early in their careers but most of the bullet points about why big companies are helpful are only applicable for senior team members. For junior people almost all of these would be faster/easier to accomplish at a startup where you've negotiated for more salary/less equity.

Re: Why you should join a big company first

#4
This really resonated with me, I was one of those cocky, over-achieving kids who thought I could start a company fresh out of college.

Instead, I've worked in Product for 26 months and learnt some really good skills: how to write real requirements, how to manage expectations (up and down), how to negotiate, how to measure and to focus on moving the needle, how to build a GTM plan and execute against it, how to deal with fireman issues, how to develop with a SOA, the list goes on.

And picked up a bunch of payments industry expertise along the way.

I'm still determined to start my own business, but definitely a hell-of-a-lot more confident in my chances of success.

Re: Why you should join a big company first

#6
This is clearly from a business perspective.

But if you're an engineer, I personally think that working for a big _software_ company early in your career is important. It's just plain easy to work on software in a small company because you don't have legacy code, existing products, existing customers, existing practices. Also you have no real way to judge whether your code is good or bad until its come under the glare of experienced engineers.

Also, people shouldn't take any of Robert Scoble's advice.

Re: Why you should join a big company first

#7
Great article, but as usual I'm put off by how the headline frames this as universal advice, a practice that's reached epidemic proportions in blogging. If this comment were a post on my blog, I might call it "Shooting people who frame their advice as universal and why you need to do it"

Re: Why you should join a big company first

#8

The article opens with the question: > “Should I join Microsoft or a startup?” but really seems to answer the question: > "Should I join Microsoft or start a startup" which is really very different.

Yeah, I was a bit confused by what the author meant.

I can see it not being a good idea to start your own startup super early for the reasons the author lists. I don't think there's anything wrong with joining a growing startup early on, though.

Re: Why you should join a big company first

#9

The article opens with the question: > “Should I join Microsoft or a startup?” but really seems to answer the question: > "Should I join Microsoft or start a startup" which is really very different.

Exactly I suggest to change the title cause it is misleading.
Post reply on HN