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.
A Competitive Programmer's Handbook
21–30 of 171 posts
Re: A Competitive Programmer's Handbook
#22great 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…
Re: A Competitive Programmer's Handbook
#23Competitive 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.
Re: A Competitive Programmer's Handbook
#24Earlier 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.
Re: A Competitive Programmer's Handbook
#25Competitive programming = coding challenges, like Google Code Jam and HackerRank. Nothing to do with getting a better job or a better salary.
Norvig seems to think it's a negative signal though. https://www.youtube.com/watch?v=DdmyUZCl75s
Re: A Competitive Programmer's Handbook
#26Earlier 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.
Re: A Competitive Programmer's Handbook
#27great 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…
Re: A Competitive Programmer's Handbook
#28There 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…
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).
Re: A Competitive Programmer's Handbook
#29Earlier 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.
Re: A Competitive Programmer's Handbook
#30Competitive 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
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.