'Every programmer should tackle these at some point before they die' =/= 'every programmer should have done this before they interview for a job'.
Let me clarify - the process by which commenters gleefully (damn that’s a nice word) add things to the list is illustrative of how things got added to the interview process. No one ever said something (or anything) should be done before interview.
Now as for “tackling before you die”.
If your name is Bobby Wagner, than by all means, tackle, it’s your job, but please do not die.
If you are programmer, you are not obliged to neither.
An interview process is completely different. An interviewer who loads up a process with nonsense is a prat, and is actively decreasing the quality of their hires.
”An interviewer who loads up a process with nonsense is a prat”
It’s not one person - it’s the entire industry. All of us.
Clearer?
I strongly disagree.
I've been through good and bad interview processes.
From my perspective, the bad processes are a good signal for companies I wouldn't enjoy working at.
By the way, you can reply by clicking the 'N minutes ago' link to open the thread.
Thanks. Didn’t know that.
I was under the impression the “reply” link is removed when levels get deeper as part of an “anti flame” system.
@dang?