At this weeks Wellington .NET user group, James asked me how I find stuff - when I need to find out how to get something done, how do I find the information I need. Here’s what I told him.


There are a number of simple tricks that often bring back useful results.

  • Add C# as a search term to constrain the results to those that mention the language I’m using

  • Adding MSDN means that results from MSDN tend to come to the top of the pile. Interesting that this is often faster than searching MSDN directly.

  • Using to search Microsoft Blogs directly is also useful.


Dan Appleman believes that one of the major impediments we face today, as developers, is one of discoverability - how do we find out what we need to know. His response to this problem is searchdotnet a search engine for just .NET material. SearchDotNet is a Custom Google Search, so you get all that pagerank goodness, but with a dedicated .NET flavour.


I read a lot of blogs to stay up to date with what is happening in the field - a useful side effect of this is that I’m often aware of others who are already working in an area when I have a problem. This gives me additional search terms to use that are often useful - for example, when searching for a solution to an NHibernate problem, adding “ayende” to the search often brings the useful results to the top.


blog comments powered by Disqus
Next Post
Two dangerous little words  16 Jul 2009
Prior Post
Exception Inspection  15 Jul 2009
Related Posts
Browsers and WSL  31 Mar 2024
Factory methods and functions  05 Mar 2023
Using Constructors  27 Feb 2023
An Inconvenient API  18 Feb 2023
Method Archetypes  11 Sep 2022
A bash puzzle, solved  02 Jul 2022
A bash puzzle  25 Jun 2022
Improve your troubleshooting by aggregating errors  11 Jun 2022
Improve your troubleshooting by wrapping errors  28 May 2022
Keep your promises  14 May 2022
July 2009