News for hackers. Stuff that matters.
Re:Competitive Programmer's Handbook (2017) [pdf] by RockmanX on Sunday April 29, 2018 @03:45PM (#16953566)
The point is why people have to remember them ?

Why not look them up when necessary ?

Re:Competitive Programmer's Handbook (2017) [pdf] by maxerickson on Sunday April 29, 2018 @09:16PM (#16955024)
I guess most of the problems are relatively small, but for Advent of Code¹, the "competitive" people are finishing most of their solutions in a minute or two.

1. http://adventofcode.com/

Re:Competitive Programmer's Handbook (2017) [pdf] by svat on Sunday April 29, 2018 @08:22PM (#16954782)
How will you look it up when necessary during a programming contest (like the IOI/ICPC mentioned in the book)? It's usually not allowed by the contest rules to look up an entire book's worth.
Re:Competitive Programmer's Handbook (2017) [pdf] by jnordwick on Sunday April 29, 2018 @07:12PM (#16954439)
And if your teams algo and data structure knowledge isn't at the level where you know about these solutions or their applicability?

I have a checklist of possible interview topics and I think I might an esoteric data structure part to it (knowledge not code) and some implementation choice questions - given this situation and data, with these queries what would your data structures look like.

Maybe also a few quotations on the last paper they've read in CS or related topic.

Re:Competitive Programmer's Handbook (2017) [pdf] by fjsolwmv on Sunday April 29, 2018 @04:15PM (#16953704)
Why test for anything in an interview? Why not assume anyone can learn everything on the job?
Re:Competitive Programmer's Handbook (2017) [pdf] by leshow on Sunday April 29, 2018 @11:15PM (#16955436)
Why even have the interview? Why not just hire everyone who applies and assume they can do the job?

There are tests and interviews because not everyone can