Difference between revisions of "How-to-Google"
Jump to navigation
Jump to search
m (→) |
|||
| Line 6: | Line 6: | ||
* Only use important words, instead of full sentences | * Only use important words, instead of full sentences | ||
* Use descriptive words and simply rephrase searches, if no good results show up | * Use descriptive words and simply rephrase searches, if no good results show up | ||
| − | * Use quotes <code>" | + | * Use quotes around your search words <code>"search words"</code>, to tell Google to use exact matching for the text within quotes, asterisks <code>*</code> can be used as wildcards to match any text |
* Use hyphens <code><ambiguous search> -<one matching field></code> to explicitly tell Google to exclude words from the search | * Use hyphens <code><ambiguous search> -<one matching field></code> to explicitly tell Google to exclude words from the search | ||
Revision as of 14:14, 31 May 2019
General
- Keep the Google search as simple as possible only being specific where necessary
- Gradually add search terms, if you do not get good results
- Try to search with professional terms, instead of natural speaking language
- Only use important words, instead of full sentences
- Use descriptive words and simply rephrase searches, if no good results show up
- Use quotes around your search words
"search words", to tell Google to use exact matching for the text within quotes, asterisks*can be used as wildcards to match any text - Use hyphens
<ambiguous search> -<one matching field>to explicitly tell Google to exclude words from the search
Dealing with Error Messages
- Just copy the error message from the command line to the Google search bar
- Remove system specific details like the system name or paths
- Though you should keep the file name, if it corresponds to a provided or system source code file