Live data from Hacker News

Competitive Programmer's Handbook (2017) [pdf]

cses.fi

31–40 of 127 posts

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

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

That’s the entire point of those kinds of interviews. It’s a strong filter for “recent graduate” while maintaining plausible deniability for ageism. It has a secondary effect of filtering for “willing to do unpaid overtime”.

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

#32
post #17

Earlier quoted context omitted.

Code should be written for readability, not typing speed.

This is not production quality code that is running on some important business. It's competitive programming. Speed is the goal here.

This is not production quality code that is running on some important business.

Then why is it used in the interview process for the latter?

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

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

If you really needed to remember it, you could employ spaced-repetition: https://en.wikipedia.org/wiki/Spaced_repetition

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

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

This is true for lots of things though, right? Programming languages, spoken languages, mathematics, muscle mass...use it or lose it, but it gets easier to re-learn/re-gain everything each time. Plus you don't necessarily have to forget or lose it if you're able to set aside the time to maintain it.

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

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

The point is why people have to remember them ?

Why not look them up when necessary ?

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

#36
post #21

Earlier quoted context omitted.

LOL

He's not joking though. I've experienced 3 rounds of stupid tricky questions followed by a 4 hour "take home" project at a UK startup in Deep Learning before they were willing to even send flight tickets to London, and the feedback I've received was so comical that I almost wrote a blog post about it (I still might). Another robotic startup in SV grills with 6-hour stupid codility tests as a first phase (i.e. waste 6…

Oh I agree! Not sure who downvoted me but I’ve been dealing with the same shit for quite some time (https://news.ycombinator.com/item?id=16127697).

The shit is ridiculous.

EDIT: Please write that blog post!

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

#37
post #32

Earlier quoted context omitted.

This is not production quality code that is running on some important business. It's competitive programming. Speed is the goal here.

This is not production quality code that is running on some important business. Then why is it used in the interview process for the latter?

I don't think code shortening is ever used for interview questions?

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

#38
post #31
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.

That’s the entire point of those kinds of interviews. It’s a strong filter for “recent graduate” while maintaining plausible deniability for ageism. It has a secondary effect of filtering for “willing to do unpaid overtime”.

Maybe it's just a way to provide a fair test that anyone with ability can pass with a little practice?

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

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

The point is why people have to remember them ? Why not look them up when necessary ?

Why test for anything in an interview? Why not assume anyone can learn everything on the job?

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

#40
post #31
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.

That’s the entire point of those kinds of interviews. It’s a strong filter for “recent graduate” while maintaining plausible deniability for ageism. It has a secondary effect of filtering for “willing to do unpaid overtime”.

I think its more of aptitude test in a domain common to all programmers.
Post reply on HN