3 ms·
It is really amazing, when you get into it, how many people with excellent-looking CV and experience just can't code their way out of a wet paper bag. They don
by ncmncm 8y ago
It is really amazing, when you get into it, how many people with excellent-looking CV and experience just can't code their way out of a wet paper bag.
They don't know what cache is or how to tell when you've run out of it; can't use pointers, can't write a loop; don't understand object lifetime or that objects have one; or think a null pointer is, or should be, the same as an empty string. (This last is most amazing because it seems to be official policy at Google!)
The elementary coding and debugging exercises that are so annoying are necessary because most candidates, by far, can't begin to do them -- MS:CS, real-time OS thesis project, and N years experience notwithstanding. What have these people been doing?
I have seen brainteasers used well, but only as a jumping-off point for a conversation that tends well away from the puzzle.
I used to use a design problem (no coding) that bright undergrads solved in two minutes, BSes in five, MSes in 20, and PhDs either never, or as fast as an undergrad. Everyone who solved it used identically the same hand gesture when describing the solution.
ITA Software used to publish great programming puzzles that you were invited to solve and send with a CV. (Google bought them out and eventually took down the puzzles, back in 2010, but they might still be in wayback). To learn how your solution compared to theirs, you had to send it! It might not work so well anymore, since everything gets posted nowadays.