Comment by Adrien N. on "How can a beginner developer master the art of Googling?"

It is a master art indeed. - and probably the most useful when it comes to code: finding the information you need.

The way I see it, there's two kind of googling:

A) my-shit-is-not-working kind of problem and "How to do that specific task" kind of question eg.
- "_{techno_xyz}_ update all info X when..."
- "Event {X} is not fired {_techno_xyz}_..."
B) tools searching and wider subject eg. "vision" problematic & so on;
- "Is it better to do X or Y ?"
- "Best practices for X"

For both I tend to first write the silliest query, in my own words which most of the time makes me read 3 or 4 links giving me the real keywords to use after that.

For A), "X is not working" is a good start when I don't have the right vocabulary or a specific error message. "How to" is also a good companion. Also for bugs/problems I always make a stop by the issues of the Github, always someone having the same or related issue even if it's a closed issue.

For B) "X best practices" works well, same as "X explained" or "why use X over Y". For tools search gitlogs.com is a must-have!

In the end, my whole method revolves around finding the right keywords, opening a LOT of tabs, reading and sorting – and keeping them open for 2 weeks 🙄 – and loop.

PS: I have a Trello board where I keep my most interesting links with a contextualization: "Really good explanation of X" or "Library for Y. Seems interesting but only 0.0.4 (2017/03/01)." or "X vs Y vs Z. Comments where really helpful."

Search Hashnode