3 ms·
I interview people based on their ability to cheat on the assessment, as finding the answer and adapting it efficiently more closely matches the day to day job.
by vmception 5y ago
I interview people based on their ability to cheat on the assessment, as finding the answer and adapting it efficiently more closely matches the day to day job.
The person that figures out how to copy and paste code for a REST call in that particular framework will still probably fail if they don't notice that they need to adapt it for the network request caching system and the ORM.
But there is no reason to memorize all that syntax and regurgitate it in the most computationally efficient Big O
- pistoriusp 5y agoI think we may be thinking about this differently. I value reading the documentation of libraries that I'm using. I don't memorize it, but casually read over it to understand what's possible. I do not do this for everything, but if it's a piece of technology that I value, then it's probably a good idea to read the docs so that I'm not faced with "I did not know that it could do that" situation. The amount of times I've seen developers painfully code around something that was already supported in the library they're using is suprizing.
- vmception 5y agoI've had a handful of developers do this, mostly in frontend work with lifecycles because they didn't read