Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Competitive Programmer's Handbook

cses.fi

Post reply on HN
Print view View original

51–60 of 171 posts

Re: A Competitive Programmer's Handbook

#51

Post by cyorir »

40acres wrote: post #7
user5994461 wrote: post #4

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.

I can do well enough on programming challenges at a place like HackerRank. However, I very rarely actually get to the technical interview in a job application; most commonly, I apply and don't hear back from the company. So as far as I'm concerned, I need better something but that something isn't better skills.

Re: A Competitive Programmer's Handbook

#53

Post by paulsutter »

cossatot wrote: post #38
paulsutter wrote: post #24

Earlier quoted context omitted.

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.

I had to compete for my job, in which I get to spend a lot of time working relatively unconstrained on scientific problems of my choosing, as long as they're quite broadly mission-oriented. I like working on questions no one else is asking and avoiding the 'a large debate exists in the community as to whether X or Y' messes that Nature loves to publish. I had to compete for my wife, who supports me and inspires me an…

Elon Musk and Steve Jobs never spent time responding to competitors. VC funding is another example. Fundable companies are so rare that VCs never sit around debating whether to fund company A vs company B, it's two separate decisions.

It sounds like what you treasure most about your job is that you're released from competing. Finding a relationship is about fit, and a good relationship is about the investment you make. I've never seen competing to work in any phase of a relationship.

Re: A Competitive Programmer's Handbook

#55

Post by cyorir »

throwaway_374 wrote: post #23
40acres wrote: post #7

Earlier quoted context omitted.

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.

I'd love it if there were more opportunities from companies like HackerRank. It's other "filters" that I'm worried about; companies that filter out degree-less candidates, companies that filter out depressed candidates, companies that filter out transgender candidates, etc.

Re: A Competitive Programmer's Handbook

#57

Post by rattray »

dsacco wrote: post #46
gpawl wrote: post #44

Earlier quoted context omitted.

Relax, parent poster was simply clarifying that the 'competitive' referred to programming "sports" contests, not competing for a programming job.

Sure, but I don't think a good faith interpretation of the title would require that sort of disclaimer, and look at the rest of the thread that resulted.

I hadn't heard of "competitive programming" before, and at first assumed this was a post exactly about "getting a better job or a better salary" (the most likely alternative interpretation).

So I was grateful for the clarification, and didn't take it as algorithm-hate.

Re: A Competitive Programmer's Handbook

#58

Post by bergie3000 »

shahzeb wrote: post #56
mattdodge wrote: post #52

Great timing considering Google Code Jam Round 1 starts tonight too

Link? / What is it? / Is it a good thing to test out for beginners?

Here's the link, but the qualification round for this year has already passed. https://code.google.com/codejam/

Re: A Competitive Programmer's Handbook

#60

Post by atemerev »

OK, who has published cheat codes for most programming interviews?

Seriously, if you can program at all, and want to be a better programmer (like, really well paid one), this is the greatest single thing I ever saw for this purpose. Just run through all examples and understand how they work, and you are already in top 1%.

Then, you can move to SICP and Project Euler in your spare time.

Post reply on HN