Live data from Hacker News

A Competitive Programmer's Handbook

cses.fi

11–20 of 171 posts

Re: A Competitive Programmer's Handbook

#11

Competitive programming = coding challenges, like Google Code Jam and HackerRank. Nothing to do with getting a better job or a better salary.

I wish this was true. If you are good at competitive programming, it is more than likely that you will be good on the whiteboard interview questions for a software developer position.

Re: A Competitive Programmer's Handbook

#12
post #7

Competitive programming = coding challenges, like Google Code Jam and HackerRank. Nothing to do with getting a better job or a better salary.

The same skills used in competitive programming are needed to pass a modern day technical interview at some of the larger companies. So I wouldn't necessarily say it has nothing to do with getting a better job or salary.

Staying fit also helps job performance, as does public speaking.

Shall we start a comprehensive list of skills and activities tangentially related to making more money?

Re: A Competitive Programmer's Handbook

#13
post #9

Earlier quoted context omitted.

In the sense of "this article has nothing to do with jobs or salaries," I would rate the claim true. The article has not one mention of either. If you're trying to argue that improving your skillset makes you more employable, sure, but that's such a general statement that I'm not sure it holds up as a retort.

I think the GP means that problems solved in programming competitions are similar to what you'll find on some job interviews.

Sure, and I think the comment he replied to means "the term competitive is ambiguous, let me clear it up: this is not talking about advancing your career."

Re: A Competitive Programmer's Handbook

#15
post #7

Competitive programming = coding challenges, like Google Code Jam and HackerRank. Nothing to do with getting a better job or a better salary.

The same skills used in competitive programming are needed to pass a modern day technical interview at some of the larger companies. So I wouldn't necessarily say it has nothing to do with getting a better job or salary.

[deleted]

Re: A Competitive Programmer's Handbook

#18

Competitive programming = coding challenges, like Google Code Jam and HackerRank. Nothing to do with getting a better job or a better salary.

Especially given the importance of teamwork. Competitive people tend towards tedious one-upmanship. It's something you want to screen out in the hiring process.

Re: A Competitive Programmer's Handbook

#19

great stuff.read this,understand this and you'll get google offer for 350k per year.

Why would you? How is knowing (and understanding) all that worth 350k per year? It shows that you are sharp and know your algorithms...is that all it takes to solve "350k yr" class problems? What do those problems look like? I suppose if they look just like hacker rank or something, then yes...

Certainly some companies put all their faith in those type of demonstrations of skill, I grant you...I'm just wondering if you or others really believe you are "Google material" by that measure.

Post reply on HN