Live data from Hacker News

A Competitive Programmer's Handbook

cses.fi

21–30 of 171 posts

Re: A Competitive Programmer's Handbook

#21

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.

Competitive people are often very good at working in teams, see any team sport, or team programming contests.

Re: A Competitive Programmer's Handbook

#22

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 y…

[deleted]

Re: A Competitive Programmer's Handbook

#23
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.

Sadly the proliferation of sites like HackerRank (YC funded shamefully) means competitive programming is the first "filter" stage for interviews these days.

Re: A Competitive Programmer's Handbook

#24

Earlier quoted context omitted.

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.

Competitive people are often very good at working in teams, see any team sport, or team programming contests.

I would choose a person who is driven to solve problems over a person who is driven to exceed others, every time. Competition is for losers.

Re: A Competitive Programmer's Handbook

#25

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

Agree with other comments about similarity to interviews.

Norvig seems to think it's a negative signal though. https://www.youtube.com/watch?v=DdmyUZCl75s

Re: A Competitive Programmer's Handbook

#26

Earlier quoted context omitted.

Competitive people are often very good at working in teams, see any team sport, or team programming contests.

I would choose a person who is driven to solve problems over a person who is driven to exceed others, every time. Competition is for losers.

Ok you must love competitive programmers then, because they are very driven to solve problems :)

Re: A Competitive Programmer's Handbook

#27

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 y…

if you live in bay area you would understand. this is how it works in US west coast. Wall street is pouring money to here and big companies just pay that much to new grads who can do algorithm questions on whiteboard. believe it or not, it is true.

Re: A Competitive Programmer's Handbook

#28

There should be references to problems for each topic at online judges. Like this one: https://uva.onlinejudge.org/index.php?option=com_onlinejudge... Learning algorithms per se is only a small part of training. Much bigger part of training is learning how to recognize these algorithms in problems. After reading about some algorithm, I always solve a couple of related problems. P.S. Looks well-written. Bookmarked. I…

The book I recommend to people getting started is Competitive Programming 3 [1] by Steven and Felix Halim. It's pretty great if you have already a basic grasp of simple algorithms and a bit of C++.

And as you say you need to practice, and the book incentivizes it. They accompany the book with precisely problems from UVa Online Judge, some of them solved and with code (in the book and in the site).

[1] https://cpbook.net/

Re: A Competitive Programmer's Handbook

#29

Earlier quoted context omitted.

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 y…

if you live in bay area you would understand. this is how it works in US west coast. Wall street is pouring money to here and big companies just pay that much to new grads who can do algorithm questions on whiteboard. believe it or not, it is true.

I don't know where you're getting those figures from, but they're off by more than a factor of 2 based on information I have from friends in Google and previous disclosures here on HN by Googlers. Google won't pay most new hires out of school much over $100k in the bay area, and they adjust based on living expense. AFAIK the higher end of junior compensation is close to $200k, which is where you start getting into the entry senior level salaries. There certainly are engineers at Google getting paid $350k in base + bonus compensation but they're not people who only know how to do basic competition problems and enough theory to get a 4 year degree.

Re: A Competitive Programmer's Handbook

#30

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

Agree with other comments about similarity to interviews. Norvig seems to think it's a negative signal though. https://www.youtube.com/watch?v=DdmyUZCl75s

I wouldn't say he considers it a negative signal considering how he said if he had to pick someone off the street he would prefer the one who is good at programming competitions.

However if you are above the bar required to get hired by google, then a higher success rate in programming competitions correlates negatively with job performance.

Post reply on HN