3 ms·
I'm not sure about the point of your post, but to respond: 1) No - you screen those out with spelling mistakes in their resume 2) Maybe? I'm not sure - I'm no
by swsieber 10y ago
I'm not sure about the point of your post, but to respond:
1) No - you screen those out with spelling mistakes in their resume
2) Maybe? I'm not sure - I'm not an electrical engineer. Then again, credentialing an EE is probably easier than a programmer.
3) This one's not even a good analogy - of course not.
What makes programming a little different is that it's turtles all the way down. While you might not need to find the average of an array, you will need the ability to reason about such things. You'll be reducing a collection of items, or mapping them or summing them.
You basically must deal with abstraction as a computer programmer. (And I'd argue that yes, assembly deals with abstraction)
- white-flame 10y ago1) But you don't use the resume to detect whether somebody is blowing BS about their software understanding? 3) It's a very apt analogy. Tons of especially lower level candidates are doing weird tricky CS problems at interview even if they're building yet more basic reporting systems. Regarding abstraction, why don't you ask them to describe projects they did, instead of grilling them on concocted problems you know are beneath the level of person you wish to hire?