This is a wonderful article on using StudioShell with the visual studio debugger.

This artictle shows how to script the local variables of the currently debugged process.
Given StudioShell has out-html and out-chart this allows the dynamic creation of visualised data straight from the current debug session.

StudioShell is a powershell console that is embedded into visual studio (it can also be invoked from the NuGet console).
It exposes the visual studio extension api known as dte as a set of powershell scripts.

BooleanToVisibilityConverter does not appear to work as expected in Silverlight 4.

This will magically return true for a missing value. This is annoying when you expect the value to be hidden.

This is a very useful addition to Nuget.

http://nuget.org/packages/AddReference

It allows command-line addition of packages to the current project.
It appears that if you need to add an explicit path (i.e. outside current directory or gac) then you can include the file extenstion.

http://learnyouahaskell.com/

http://learnyousomeerlang.com/

This comment seems to be appearing in my code rather more frequently recently, especially as I have been working with WCF.
This should include the important information which tool generated the file, include version information and parameters used.

WCF code generation is rather weak. It includes 7 wierdly named hidden files. One of these includes a url reference to the web service that generated the client proxy.
If the config file for the service fails to include a reference to the service then the service that generated the client is used. This is very dangerous and will make production code accidently refer to a test server.

Here

This is an alternative to the good old vimtutor.

http://www.openvim.com/tutorial.html

And for those scared of vsvim there is always ctrl-shift-F12 which enables/disables vsvim.

Here is a link to a book on programing software in python for kids.