You're looking at Less Wrong's discussion board. This includes all posts, including those that haven't been promoted to the front page yet. For more information, see About Less Wrong.

Jayson_Virissimo comments on Open thread, 24-30 March 2014 - Less Wrong Discussion

6 Post author: Metus 25 March 2014 07:42AM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (156)

You are viewing a single comment's thread. Show more comments above.

Comment author: [deleted] 26 March 2014 06:49:04PM 3 points [-]

It seems clear that for people with a bachelor's in CS, from a purely monetary viewpoint, getting a master's in the same area usually is dumb unless you plan on programming a long time.

This article says the average mid-career pay for MSc holders is $114,000. This says the mid-career bachelor's salary is $102,000. A master's means 12 to 24 months of lost pay and anywhere from a $20,000/year salary in some lucky cases to a $50,000+ debt. You need at least a decade of future work to justify this. And that likely overstates the benefits since it does not control for ability.

I don't necessarily trust these statistics but employers can always make people write code on whiteboards to assess actual skill.

An exception might be if you want technically cutting-edge CS: Google for example prefers MSc/PhD guys. But I think most programming jobs are not like that.

Comment author: Jayson_Virissimo 28 March 2014 04:16:49PM 2 points [-]

FYI, it is possible to do a part-time masters program and some employers will pay for you to get a graduate degree (usually as part of an agreement to keep working for the company several years afterwards).