Live data from Hacker News

Competitive Programmer's Handbook (2017) [pdf]

cses.fi

111–120 of 127 posts

Re: Competitive Programmer's Handbook (2017) [pdf]

#111

I would watch programming contests live streams.. Are there any available?

In my experience, most of the time goes into coming up with an algorithm or debugging. I don’t know about you, but I don’t think those would be particularly interesting to watch.

I am mostly just fascinated by people able to stream their coding. I think most of my stream would consist of googling stuff and procrastinating on hacker news and tabloids

Re: Competitive Programmer's Handbook (2017) [pdf]

#112
post #74

Earlier quoted context omitted.

Give us a frelling break. Please don't willingly invite derison.

It's not ok to comment like this here, regardless of how wrong someone else is or you feel they are. Please post civilly and substantively, or not at all. https://news.ycombinator.com/newsguidelines.html

Sorry, it was indeed an off-the-cuff remark in poor taste.

Re: Competitive Programmer's Handbook (2017) [pdf]

#113

Earlier quoted context omitted.

I'm not sure that you avoid errors by forcing yourself to write short code. With C macros.

When you write "FOR(i,n)", instead of "for (int i = 0; i That being said, I've found that competitive programmers sometimes write extremely ugly code. It's surprising to see how they are able to solve such complex problems, and yet can't (or don't value) write readable and structured code. Maybe they are so sharp that they don't feel the need to make their code more readable.

Well, when your code has a lifetime of five hours max, readable doesn't matter, correct does.

Re: Competitive Programmer's Handbook (2017) [pdf]

#114

Earlier quoted context omitted.

But if you're in a competitive environment that requires speed, why would you write for readability?

Because you’ll end up debugging the code an hour later when it fails on an edge case?

The really good competitors won't make that sort of mistake...

Re: Competitive Programmer's Handbook (2017) [pdf]

#115
post #52

Earlier quoted context omitted.

Sure, that might be the case. But for those funny needs I have a "crazy algorithm course" from a top 10 university, ACM ICPC and Kaggle or other paid competitions I can attend. I am not going to go through such an interview doing simple silly things I did dozen times before at FB/Goog/etc., when I know I can use that time to work on something more interesting, or just for relaxing after a hard work/enjoying accomplis…

I have a sneaking suspicion that I’ve built a feature that was presented as a coding exercise, possibly more than once.

Imagine you get that very feature during some interview and the feedback you get is that you failed :DDD Reminds me when I created a few jokes as a kid that got nation-wide popularity; it was difficult to explain I made them from the scratch and the only thing those attempts gave me was to be marked as an "asshole" and "liar" :D

Re: Competitive Programmer's Handbook (2017) [pdf]

#117
post #52

Earlier quoted context omitted.

The problem is, for every person like you, there's a person like me that actually likes those types of challenges and wouldn't actually mind being thrown into that type of gauntlet. My years of experience be damned.

Sure, that might be the case. But for those funny needs I have a "crazy algorithm course" from a top 10 university, ACM ICPC and Kaggle or other paid competitions I can attend. I am not going to go through such an interview doing simple silly things I did dozen times before at FB/Goog/etc., when I know I can use that time to work on something more interesting, or just for relaxing after a hard work/enjoying accomplis…

There's irony. Asking for GitHub is 10x worse than algorithmic questions. I just went through the interview process at big companies, with all the resources out there it's easy to get good at these types of questions.

During my professional time I write software to make money. During my free time I write software to make money. As an aging software engineer algorithmic questions just screen for how much time you're willing to put into an interviewing. GitHub screens for how much of a sucker you are.

Re: Competitive Programmer's Handbook (2017) [pdf]

#118
post #29

The most irritating thing with these competitive/algo stuff is that no matter how many times you master it - eventually you always forget it, because you don't need it on a daily (or more like yearly) basis in the real world.

Just like sql and regular expressions. You work hard to get it to work and then forget about it.

Re: Competitive Programmer's Handbook (2017) [pdf]

#119
post #52

Earlier quoted context omitted.

Sure, that might be the case. But for those funny needs I have a "crazy algorithm course" from a top 10 university, ACM ICPC and Kaggle or other paid competitions I can attend. I am not going to go through such an interview doing simple silly things I did dozen times before at FB/Goog/etc., when I know I can use that time to work on something more interesting, or just for relaxing after a hard work/enjoying accomplis…

There's irony. Asking for GitHub is 10x worse than algorithmic questions. I just went through the interview process at big companies, with all the resources out there it's easy to get good at these types of questions. During my professional time I write software to make money. During my free time I write software to make money. As an aging software engineer algorithmic questions just screen for how much time you're w…

Yeah, could be. Though if you provide a hiring company with a GitHub profile demonstrating your dominance, and then you are expected to waste another 6 hours on trivial algorithmic questions you probably did 100 times in the past 10 years, you'd probably just pass on that "opportunity". Those algorithmic questions were anyway originally meant to find the "best of the best", now they are used for entry-level positions. It's like asking an accomplished lawyer about what happened in 1758 and what was the effect on common law.

Re: Competitive Programmer's Handbook (2017) [pdf]

#120

I see in the comments that some people conflate competitive programming and technical interviews. Technical interviews (at least in companies such as facebook and google) are usually much easier than competitive programming problems. The problem you find on leetcode for interview preparation would be considered beginner problems in competitions such as google code jam.

> Technical interviews (at least in companies such as facebook and google) are usually much easier than competitive programming problems. Probably. But if you are a student outside U.S where the opportunities are an order of magnitude less the only way to even land an interview with these companies is by doing competitive programming. Google selects students through APAC test in Asia where you have to be top n% in th…

> All the persons I know of in my country who works at Google or Facebook got their job through competitive programming.

Are any of them bad developers?

Post reply on HN