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.
Competitive Programmer's Handbook (2017) [pdf]
31–40 of 127 posts
Re: Competitive Programmer's Handbook (2017) [pdf]
#32Earlier 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.
Then why is it used in the interview process for the latter?
Re: Competitive Programmer's Handbook (2017) [pdf]
#33The 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.
Re: Competitive Programmer's Handbook (2017) [pdf]
#34The 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.
Re: Competitive Programmer's Handbook (2017) [pdf]
#35The 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.
Why not look them up when necessary ?
Re: Competitive Programmer's Handbook (2017) [pdf]
#36Earlier 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…
The shit is ridiculous.
EDIT: Please write that blog post!
Re: Competitive Programmer's Handbook (2017) [pdf]
#37Earlier 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?
Re: Competitive Programmer's Handbook (2017) [pdf]
#38The 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]
#39The 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]
#40The 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”.