Many people have mentioned it and it is true for the most part that memorizing syntax, functions, parameters, design patters, etc... is not really necessary but I want to say that memorization is very valuable as well.
Think of your memorization skill as a cache and looking up things on Google as a hard disk read. The more things you can put into cache (aka memorized) you can develop things quicker, you can manipulate and simulate situations faster.
If at all possible, try to memorize the things you do quite often. The less you need to fetch data from a hard disk (Google) the faster and quicker you can do things.
True, if you use something often then it can very well be worth memorizing ... still, as a company I'd put more emphasis on the candidate's knowledge of the ecosystem around a tech stack, and the ability to design a complete "real world" solution (at least for a senior dev)
Many people have mentioned it and it is true for the most part that memorizing syntax, functions, parameters, design patters, etc... is not really necessary but I want to say that memorization is very valuable as well.
Think of your memorization skill as a cache and looking up things on Google as a hard disk read. The more things you can put into cache (aka memorized) you can develop things quicker, you can manipulate and simulate situations faster.
If at all possible, try to memorize the things you do quite often. The less you need to fetch data from a hard disk (Google) the faster and quicker you can do things.
True, if you use something often then it can very well be worth memorizing ... still, as a company I'd put more emphasis on the candidate's knowledge of the ecosystem around a tech stack, and the ability to design a complete "real world" solution (at least for a senior dev)
Great example. Thank you for your advice!