The title is a mouthful and accurately implies an alarmingly high jargon to code ration, but I just didn't see anyway to write this post without straying into all of these different subjects. When you try to write an explanatory article you have to walk a tightrope between a sample problem that's...

When last we left our hero , D'Artagnan was chasing the evil Lady de Winter across the breadth of France trying to intercept her on her dastardly mission when he found himself beset by disparate responsibilities within the tight confines of a single autonomous view with no room for sword play. D'Artagnan...

The slide deck and sample code from my StructureMap talk last night is available from the ADNUG downloads page . Thanks to Jeffrey Palermo for inviting me and everybody who attended. If you're using a different DI tool than StructureMap, we spent a lot of time talking about possible usages for DI tools...

In my Third Law of TDD Liang asked me in a comment: "Could you let me know if you have a basic application architecture design in mind before you write the first line of code? Or you just let the test/code lead you to a design. For example, if you find a common method in related classes, you create a...

Laws of TDD is probably something that should be written by someone with more authority in the community, but I've got a blog and I thought of it first, so here goes. I'll expound on each of these at some point in the misty future, but just for fun here is Jeremy's Laws of Test Driven Development (I...

DISCLAIMER: This was written all the way back in Feb. 2006 when we MVP with ASP.NET was the only real alternative. I thank you for the interest, but there have been better articles written since, and I'd strongly recommend looking at MonoRail or Ruby on Rails or the new MVC framework for ASP.NET...

A fairly common topic with TDD practitioners, both newbie and experienced, is how the heck to unit test business logic with a database hanging around. I’ve had several conversations lately about this so I thought I’d get a post about it. Before I try to talk about some strategies for this, here are a...

A couple of weeks ago I wrote about using the Inversion of Control (IoC) principle to create classes that are easier to unit test. One major thing I left out of that post was using the Dependency Injection pattern to loosely couple classes from their dependencies. In a nutshell, dependency injection...

Inversion of Control (IoC) is an essential tool for any software designer’s design toolbox because it’s often a great way to break dependencies between classes and promote loose coupling. IoC is vital for doing Test Driven Development without pulling out all of your hair in frustration. Real Life Example...

(IoC) is an old principle in object oriented programming, but it’s gotten a lot of buzz the last couple of years because of the proliferation of Dependency Injection (DI) tools and articles. Dependency Injection is a significant flavor of the broader Inversion of Control principle, but it’s not the whole...