3 ms·
Or they realized in that moment they didn't feel confident enough in their own understanding of state machines to critique anyone who might take the opportunity
by sennight 4y ago
Or they realized in that moment they didn't feel confident enough in their own understanding of state machines to critique anyone who might take the opportunity to cut them down to size. It is a stupid reaction to a sensible request for clarification, there are tons of equally valid ways to implement a state machine in an object oriented python script - especially when there are zero constraints on expected use. If I'd asked such a question, and got no sense of pushback, I'd be a little nervous about hiring that person and having them need close supervision - because they were to scared to point out ambiguity in direction.
- userbinator 4y agothere are tons of equally valid ways to implement a state machine in an object oriented python script ...and chances are that the interviewer would be fine with any of them, or ask questions after you've shown a solution. If I'd asked such a question, and got no sense of pushback, I'd be a little nervous about hiring that person and having them need close supervision - because they were to scared to point out ambiguity in direction. That's the exact opposite impression I have; someone who doesn't need to ask many questions, as long as they can justify their decisions well, is definitely more preferable to someone who constantly asks and needs to be lead every little step of the way.
- pasquinelli 4y agothe question was about a state machine. could there be a more general task to give a programmer? certainly no task would ever be assigned to them on the job that would be anywhere near that general. questions like that don't show you how they'll be on the job, they're an opportunity to see their thought process, but you won't get that without talking to them.
- sennight 4y ago> ...definitely more preferable to someone who constantly asks and needs to be lead every little step of the way. Asking for clarification before starting isn't anywhere close to "needs to be lead every little step". If you are hiring a work crew for roadside ditch digging than your interview method might be a good idea, but for a job where implementation details matter - bad idea. One of my more difficult professional experiences was fighting the urge to displace blame for a wasted week of work, which would have been avoided had I asked for the tasking to be described back to me - or had he spoken up and said "Do you mean this or that?"