My TechEd BOF session Pragmatic Architecture has been accepted. It's currently scheduled for Wed, June 8th at 7:45. I am really looking forward to this. Application, system and enterprise architecture are taken for granted way to often. It's not about SOA, agile, TDD etc etc etc, it's all about doing the “Right Thing”. Hope to see many of you there to take part in the discussion

Steven Cohn has a post Risk Based Unit Testing in which he describes the difference between tactical vs strategic unit testing. Tactical would be along the lines of TDD in which almost every individual method and property has a test written for it. Strategic would be testing the logical business case. This level of testing would actually test several method and property calls. The point being the test isn't as concerned with each individual method call, but the end result of making several method...

Well I finished the book Test-Driven Development in Microsoft .NET and I still feel less then satisfied. My problem with TDD stems from the test first then code idea. I like the idea of being able to test the public interface to a class, assembly etc. This can really be useful in a team development environment. An example of this happend to a co-worker today. Someone changed what was returned by a property. Not sure if anyone figured out why, but a simple NUnit test would have discovered this, and...

I have been reading Test-Driven Development in Microsoft .NET and I'm a bit disappointed. I am really trying to see the benefit of TDD, but I have to admit that it is escaping me. I see the benefit of using a tool such as NUnit or CSUnit, and plan on implementing the tool in our process. The part I'm having a hard time with is writing the test first then the code. It seems to me that by doing that you design your app to meet the tests and not to solve the business need. I know the idea is to write...