Basic route testing in ASP.NET MVC is good, but I much prefer action-centric tests.
The simplest pattern that can be used to represent fluent interfaces is to use state machines, in a usage-first approach.
IoC/DI containers usually come in bulky libraries. What happens when you want to use IoC/DI when designing small, dependency-free libraries?
No rules without exceptions. Or can this be turned on its head: Rules, just rules.
Razor's nested layouts really can save your day. But they leave something to be desired.
There is one thing I really hate when it comes to user experience on the Web: A dumb textbox for a very specific input.
Migrated the blog from Blogger and I will hopefully bring this blog back to life.
I can't stress how important immutable objects are in most designs.
The broken double-check lock: It's broken but it works.
Fluent interfaces are becoming more and more popular in C#; Thanks to Lambda expressions, Expression trees and Extension methods.
C# Extension methods; What are they?