Mortality rate (= getting the axe = being let go = being fired) would be dramatically higher between developers if Google wasn't there to keep them from falling apart (or reverting to slow and painful alternatives) every time they have to learn something new (meaning almost every day unless you are a Reporting Engineer - if so good luck with that).
I am not saying nothing new here, just that today being able to quickly find answers on Google is - if not the most important - at least the second or third most important skill of a developer/software engineer.
Said so, I tried a little experiment: I kept track of how many times I look up work-related stuff using Google during an average day of work (9 to 5 let's say):
10:05 - looked up C# 'as' operator to refresh a few concepts
10:48 - looked up COM on C# sample (there's always something wrong - if you do suck)
12:30 - looked up CoCreateInstance COM function
14:30 - looked up Abstract Factory Pattern sample (no good - Factory is enough for me)
15:55 - looked up T-SQL reference for 'collate' statement
16:40 - looked up osql to run .sql scripts from SQL through xp_cmdshell (BAD idea!)
So turns out on an average day I looked up 6 times on Google - none of those things were crucial for what I was doing but I needed to shed some light on some doubts or explore possibilities I wouldn't have had otherwise. To answer the headline, I start craving for Google after a couple of hours. After a day I would probably start to freak out. After a week or two I'd probably quit (OK , maybe not, maybe I'd switch to Yahoo before quitting). I am not able anymore to count all the times Google really made my day- and I have to say that this is the reason why I opened this blog, to participate in this awesome process of merging my experience based knowledge with the average guy out there who's probably doing the same.
In my experience sometimes people are ashamed of looking up stuff on Google - well they shouldn't be since today is more the 'look up on google skill' is more valuable for a developer than any other static skill and you don't have to waste your time trying to memorize APIs or looking for perfect references 'cause google is the perfect reference (if you know how to filter all the crap - obvious). Sometimes it is astonishing to see people that revert to Google (or the web in general) only if all other means fail after a few days of blood-sweating quests (meaning all the books on the shelves and everyone in the company have been consulted) - it is (most of the times) the other way around guys.
I won't go as far as saying that I couldn't do my job without google (did I already do that?) - but certainly I couldn't be as productive without.
OK - enough boredom for today.
P.S. if you don't agree I'd like to hear why.