Under the hood and working with .Net, TDD, Software Design, and Agile Stuff
Here's a handful of articles on designing with or for TDD I had originally posted on my old blog. I've been haphazardly trying to write about all the things I wished I'd known when I was starting to use TDD. To be honest, I think my first TDD/CI project was a mild disaster. There's a few tricks and principles to follow to keep out of TDD hell and I'll eventually get around to more content on the subject.
I'm still meaning to write about the topics below. If you've got any suggestions for future posts, feel free to send them to me and I'll see what I can do.
- Assigning Responsibilities
- Inversion of Control
- Dependency Injection (with and without a "container")
- Gateway Pattern
- Mocks and Stubs - Best (and Worst) Practices
- Untangling Code from Configuration (huge pet peeve of mine)
- Law of Demeter/Tell, Don't Ask
About Jeremy D. Miller
Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy previously worked as a systems architect building mission critical supply chain software for a Fortune 100 company and learned agile development practices as a .Net consultant at ThoughtWorks, one of the pioneers of agile development. Jeremy is the author of the open source StructureMap (http://structuremap.sourceforge.net) tool for Dependency Injection with .Net and the forthcoming StoryTeller (http://storyteller.tigris.org) tool for supercharged FIT testing in .Net. Jeremy's thoughts on just about everything software related can be found on his weblog "The Shade Tree Developer" at http://codebetter.com/blogs/jeremy.miller, part of the popular CodeBetter site. Jeremy is a Microsoft MVP for C#.
