The article was translated from medium.com , please see the original article at https://medium.com/better-programming/developer-productivity-boost-with-google-search-tips-tricks-9ae384602e22 .
There are many ways to speed up software product handover, as I mentioned in a previous article . But here, I’ll go into more detail, explaining some of the tips and tricks that I use every day to find answers faster.
Use an asterisk *
When you encounter a problem in XCode, you will normally receive an error message for a specific object. Usually, we will search for this error on Google as follows:
While you’ll often find answers to common mistakes, it’s not always effective.
You can use the asterisk. Just replace specific objects with an asterisk * , like you see in the Coyote.HomeViewController (0x1010b01f0) and Coyote.BucketListViewController (0x10bd7f580) replaced with * . Specific objects can be: application name, class name, or pointer, they are objects only in your application. The keywords you use to search on Google will be as follows:
The number of search results has increased to 578,000,000 results, compared to 2 search results without the asterisk.
As you can see in the above example, the search results are much more accurate and more likely to be exactly what you need.
Use a specific domain name
Programmer productivity can be further improved if you know where to look. If you’re looking for a code issue, for example, you might want to look for it on Stack Overflow . We can search as follows:
This narrowed the result to 810,000. The results are more specific and more likely to contain the answer we are looking for.
Use “solved” as a search term
While this is not an officially supported feature by Google, it will help increase productivity for developers by trying to filter out unresolved questions. 
This narrows the number of results to 295,000 and brings us closer to the correct answer. If you’re wondering why I put the keyword “solved” at the beginning instead of the end, it’s because it has a difference. The order of keywords affects priority and yield different search results.
Use the keyword “accepted” instead of “solved”
You may want to use the keyword “accepted” instead of “solved” on Stack Overflow. This works better because Stack Overflow marks the answers as accepted instead of marking questions that have already been solved. However, in general, “solved” seems to work better with other websites.
Will searching directly on Stack Overflow improve the programmer’s performance even further?
You may think that the above opinion is correct. However, finding the same answer on Stack Overflow’s search page was ineffective. Even when only searching for answers and questions related to Swift, including accepted answers, the search results are still quite disappointing. 
This is unique to Stack Overflow and other sites may be better or worse.
Other search examples
The above example is great for finding answers to specific programming problems. However, sometimes you want to find something else, like a document scanning library written in Swift, for example: 
Or maybe you want to find a specific post on the SwiftLee blog.
I hope this helps increase your software development productivity.