4 ms·
If you ever wondered how the tech interview process got to where it is, here is live example (of one possible explanation) - look at the comments, gleefully add
by ronilan 7y ago
If you ever wondered how the tech interview process got to where it is, here is live example (of one possible explanation) - look at the comments, gleefully adding more and more stuff.
So.
1. “Every programmer” is a matter of speaking. Obviously not every programer should try any of. Author I believe knows that.
2. If you are not a programmer you don’t add to the list. Period. You wouldn’t be adding to the list of “drills any dentist should try”, right? So why here?
3. If you are a programmer, and have not tried all of the above why are you adding more? Yah, I know, you once did a challenging project that is not on the list. So did I. “Doesn’t make me Madonna, never will”.
Now what if you are a programmer and you’ve done all on the list, with or without substitution (like Snake might be equal Space Invaders)?
In which case you’d have at least 6 repos to share with the world, and if you can implement Tic-tac-toe live, you might get to the next round of interviews.
- esotericn 7y ago'Every programmer should tackle these at some point before they die' =/= 'every programmer should have done this before they interview for a job'.
- ronilan 7y agoYour assertion is true but you missed the point. Completely. 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.
- esotericn 7y agoThe blog post is offering interesting things to do as a hobby. 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.
- ronilan 7y agoDaniel, system doesn’t let me comment below - so I’ll comment inline cause it actually matters: ”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?
- esotericn 7y agoHello! 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.
- ronilan 7y agoBy 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?
- detaro 7y agoYes, that's what's happening. Apparently hiding the reply link and forcing you to go through a different route is considered to be a compromise that hopefully stops people a bit/causes them to take note without stopping the conversation entirely.
- ronilan 7y agoEvery interaction is a learning opportunity. :)
- johnfn 7y agoI don’t understand where all this negativity comes from. The OP is just sharing some projects they found particularly fun. It’d be like a hiker saying “every hiker should climb the Stanford dish”. Nothing wrong with that, they’d just be sharing something that they found particularly gratifying.
- detaro 7y agoPeople dislike the every X should framing, because it's also often used in a negative way ("you're not a real X if you haven't", "you should invest lots of time to do these extra things", ...). If it's "a list of projects that were particularly fun" that would be great title.