- Joined
- Jun 18, 2007
- Messages
- 65,832
- Likes received
- 32,655
- Thanks received
- 10,042
- Location
- Your local branch
do you think it looks bad if you lookup books/manuals/websites whilst on site ?
I've found that being able to say that there's a solution to, or information appertaining to, some problem, and either find it online in seconds, state which book it's contained in, or walk over to the bookshelf (in those ClientCorps that have one) and turn to the relevant page of the manual and point at the relevant information is invaluable in reinforcing clients' appreciation of my expertise.
It doesn't matter if you know the answer. Knowing how to find the answer is what counts.
If a client thought I was somehow failing by looking something up rather than relying on a possibly faulty memory, I would assume that the client was itself failing by expecting the impossible. As others have suggested in this thread, nobody in their right mind would expect somebody to memorise every single method signature in the Java, .NET or PHP APIs.
FWIW, when I was in my technical interview at Y! I responded to a question by saying that I didn't know, but if I needed to I'd just look it up. One of the two interviewers turned to the other, saying "That's true - we should get rid of that question. Nobody remembers stuff like that, you just Google it."
After a momentary pause he corrected himself: "Well, you just search on Y!"... and then all three of us burst out laughing

