In this essay, sure to be included in his much anticipated book on concurrent .NET programming, Joe Duffy explains what to look for when reviewing code prior to check-in, from shared state to the ever-controversial (yet oft-overlooked) issue of code documentation.

This is an excellent, easily digestible checklist for managed-code programmers. Most interesting is his focus on the .NET Common Language Runtime memory model: "I explicitly permute (often on a whiteboard or in notepad) the sections of the code that involve shared loads and stores, using knowledge of the legal reorderings given our memory model, to see if the code breaks."

A useful resource, and an encouraging sign...