3 ms·
Worse, you simply have no way of knowing what their evaluation criteria are. Maybe they want you to be slow and thorough (I've been nailed for not checking the
by dreamweapon 12y ago
Worse, you simply have no way of knowing what their evaluation criteria are.
Maybe they want you to be slow and thorough (I've been nailed for not checking the exit status of print statements). OR maybe they want it quick and dirty, in which case you'll get nailed for "overengineering", or you just wont have time to do it the imaginary time frames they set for these tasks, if you go for any of the defensive practices that the other guy would have nailed you for. Fun, fun, fun.
- rrradical 12y agoVery much yes. In an interview I was prompted to write some code that ran as quickly as possible. 10 minutes in they were concerned that I hadn't started with a naive proof-of-concept solution and improved from there. I don't disagree with their idea of good programming practice, but how could I know they wouldn't penalize me for coming up with a slow naive solution, when the prompt specifically said to run as quickly as possible?
- danielweber 12y ago1. Tell people what you want. 2. Actually evaluate them on that. Anything else is a psychology test, and you aren't psychologists.
- RogerL 12y agoAnd you have the ever fun "I'm not worried about whether it compiles", followed up with endless "you forgot a semi-colon", "you didn't declare that variable", and so on.