Live data from Hacker News

How often do you "Google" while programming?

news.ycombinator.com

11–20 of 21 posts

Re: How often do you "Google" while programming?

#11
My search history page says ~70 queries/day on work days and ~30 on weekends - majority of that stuff is about programming. So yeah it's not a problem.

That said - I don't even bother remembering the links to documentation. When I need something I just go to "python docs multiprocessing" or similar address and hope that I'm lucky. Search is the new URL ;)

Re: How often do you "Google" while programming?

#12
I remember only 5 years a gruffy old sysadmin preaching "Can't you guys code without googling all the time? Programming is not what it used to be." I listened to his advice for a while & I'm thankful for it. I now try to do big conceptual work in offline mode but google like crazy for all the nitty-gritty details.

Re: How often do you "Google" while programming?

#13

My search history page says ~70 queries/day on work days and ~30 on weekends - majority of that stuff is about programming. So yeah it's not a problem. That said - I don't even bother remembering the links to documentation. When I need something I just go to "python docs multiprocessing" or similar address and hope that I'm lucky. Search is the new URL ;)

Same here, but that might not be the best example since there is `pydoc multiprocessing`, perhaps integrated with your editor.

Re: How often do you "Google" while programming?

#16
Technology changes fast. So fast, that now days the most effective strategy is not to know everything, but to know how to find relevant docs efficiently. Of course you also need basic skills for understanding and using them properly.. Now that, comes from experience.

Re: How often do you "Google" while programming?

#19
Its perfectly ok. A lot of times others have already ran into the particular problem and already solved it. You need to understand the solution, just don't blindly accept some random solution found on the internet. If you do this, then your code will get ugly fast and you will not know what it is doing. But there is nothing wrong with finding a solution, studying it, understanding it, and then using it in your own code.
Post reply on HN