There are some really technical things ive done in the pasy that I couldn't do without a reference right now, but once I've got the reference I don't need to be reminded about low level details or edge cases or gotchas - it's all still there in my head I just need to see the road map and it will all come back to me.
Knowledge is so easily acquired these days that, while useful, it is not essential. I hire people with zero domain knowledge for that reason.
But more problematic is when people don’t know there’s a problem to google in the first place — it seems to do the job — which is usually resolved by both education and experience, but is ultimately a result if they don’t know what they don’t know.
The knowledge is generally out there, but you need to know you’re looking for it, and it’s only in the common/trivial problems that it’s so obvious that the compiler/tooling/customer just flat-out tells you you’ve missed something
Explain this to me by looking it up. https://imgur.com/Bj24AAR
I wouldn't want to go to doc that has to Google basic stuff.
It's a statement that I agree with. There is just too much knowledge to know it all. These days there is a very real skill in knowing how to search i.e. a second order version of the above statement "you need to know where to find out how to look this up".