For about eighteen months I have chewed on an idea for something I call Distributed Continuous Integration Build. The idea has had to stew behind other priorities - like the birth of my fourth child.

The default PowerShell profile does not contain a variable for the Documents folder. Meanwhile Windows does not contain an environment variable for it either.

Ever mistype a path during Find and then have to live with it in the list forever?

Are you running Vista? Do you have dual monitors? Last question: do you have them stacked vertically?

Delegates are ubiquitous throughout .NET development though many developers are not aware of their full range.

Windows Vista introduces several security improvements paving the way for limited user account operation versus the de facto practice of privileged user account operation. In this post we look at what the two modes of operation mean to a developer and how to do some common tasks under LUA operation.

What is good practice for understanding a system? What is the point of understanding a system? How and when does that understanding become outdated? These questions are relevant to system documentation - our topic. This article seeks to directly answer each of these in turn.

The timing seems right to demonstrate a pattern for testing asynchronous processing. This follows up on Steve's assertion: Don't make assumptions, write the test.

Came across a gnarly difference in behavior between .NET runtime and Mono runtime. Take a look at this snippet.

Closures are a powerful concept in some languages - a powerful tool in others. In my mind a tool is something I can ask for by name - as in, "I'd like a reciprocating saw, please." Languages where closures are truly a tool include Lisp, Python, Ruby, among others. For the time being I will use Ruby to discuss closures - although a switch over to Lisp may be necessary.