31 ms·
Although I think I get the intended humour, the daily job certainly shouldn't be to Google answer to questions. Google to get to documentation... Sure. Reading
by okamiueru 4y ago
Although I think I get the intended humour, the daily job certainly shouldn't be to Google answer to questions.
Google to get to documentation... Sure. Reading documentation.. Sure. Ability to understanding it and how it is used, that's what would be missing, and what is suggested the interview question failed to pick up on.
- boltzmann-brain 4y agoThat's an illusion. Almost all of a coder's daily work is stuff that has been done already about a hundred thousand times. Every time I'm coding on easy mode (eg some sort of personal project where I have all the leeway) I can get through all of it just by googling $language how to $x ... been doing exactly this workflow recreationally during times when I don't feel like exerting myself for years now. It's neither slower nor does it provide worse results than in situations where I'm dealing with technologies I know inside out. With the tougher stuff, you should be consulting your colleagues anyways. If no one knows - then you research together... on google.