Thanks to everyone who came to my two sessions at the Portland CodeCamp this weekend. The NoSQL Movement, LINQ, and MongoDB - Oh My! Panel Discussion: NoSQL vs. RDBMS. You can download the slides, demo code, and the mongoctx code snippet for Visual Studio here: NoSQL + MongoDB + LINQ : [link] NoSQL vs. RDBMS Panel : [link]. If you missed the sessions and want to see some MongoDB + LINQ or if you would like to recommend this session to a friend, I'll be doing a webcast on a very similar talk tomorrow: NoSQL + MongoDB + LINQ Webcast. Cheers! mkennedy. All content copyright Michael C. Kennedy.

I'm happy to announce I'll be doing a free webcast in the DevelopMentor webcast series on MongoDB,NET, LINQ, and NoRM. NoSQL Movement, LINQ, and MongoDB. Tuesday May 25th - 11AM PST Register here. hope to see you there. We'll be building out a website in ASP.NET MVC with MongoDB as the back-end using LINQ. There will be plenty of code so it should be fun and educational. Cheers! mkennedy. All content copyright Michael C. Kennedy. All information, source code, and especially tools are provided as is and on a "use at your own risk" basis.

This article is a follow up one I wrote last week entitled “The NoSQL Movement, LINQ, and MongoDB - Oh My!”. In that article I introduced the NoSQL movement, MongoDB, and showed you how to program against it in.NET using LINQ and NoRM. highlighted two cornerstone reasons why you might ditch your SQL Server for the NoSQL world of MongoDB. Those were. Ease-of-use and deployment. Performance. For ease-of-use, you’ll have to want to read the original article. This article is about the performance argument for MongoDB over SQL Server (or MySql or Oracle). money) to burn. Think about it. Fair enough.

Lot's of time i find myself working to shorten compile and build times. While most people agree with shorter is better for compile times, the questions of what is short? and how important is it? seem to remain vague and seemly open to judgement. It's not. So I wanted to take a moment to clarify it. vBlogged my thoughts here You can see the excel sheet here and read the Joel on Software Thread here

Recently had some issues with the method assertNotNull(object) because it doesn't help with any of the 4 principles of TDD. Specifications Feedback Regression Granularity I vloged my thoughts here. Finally, here's the code I was looking at. and check out www.approvaltests.com

OK, this isn’t news, this study came out a couple of years ago and was covered by many people then. But, I find myself regularly referring to it trying to find the link. So I’m going to blog about it then I’ll always be able to find the link. The study is by Nagappan, Maximilien, Bhat and Williams and is entitled: Realizing quality improvement through test driven development: results and experiences of four industrial teams and is freely downloadable from Microsoft. The second MSN team had a defect density less than a quarter of Y but took 15% longer. TDD reduced bugs. Anyone got a link?