Monthly Archives: November 2011

The value of certifications

Posted on November 29, 2011 by Jimmy Bogard

Reading Davy Brion’s post on Does Certification Have Any Value?, he provides a common answer: Someone asked which certificate would be the better choice on Twitter today: Microsoft Certified Professional or Certified Scrum Master. My answer was very simple: neither … Continue reading →

Posted in People | 15 Comments

Dealing with transactions

Posted on November 28, 2011 by Jimmy Bogard

In the last post on NServiceBus, I got quite a few comments that one way to fix the problem of dealing with non-transactional operations that must happen if some transaction succeeds is to simply move the non-transactional operation after the … Continue reading →

Posted in Architecture | 10 Comments

Stop premature email sending with NServiceBus

Posted on November 22, 2011 by Jimmy Bogard

We use NServiceBus quite a lot to manage integration points where the other side isn’t transactional and we need to “shore up the process” of communicating with external services. One integration point we often don’t think about in terms of … Continue reading →

Posted in NServiceBus | 25 Comments

When to use NHibernate

Posted on November 18, 2011 by Jimmy Bogard

Ayende posted some guidance on when to use NHibernate: If you are using a relational database, and you are going to do writes, you want to use NHibernate. If all you are doing are reads, you don’t need NHibernate, you … Continue reading →

Posted in Domain-Driven Design | 12 Comments

The last vestiges of Hungarian notation

Posted on November 9, 2011 by Jimmy Bogard

Certain arguments seem to resurface every few years, like whether or not to use a mocking framework, and more recently on Twitter on why .NET still uses Hungarian notation in a few select cases, namely: Interfaces Generic type parameter names … Continue reading →

Posted in Rant | 21 Comments

Why do TDD?

Posted on November 1, 2011 by Jimmy Bogard

Because sometimes your test passes the first time you write it. Either you’re done writing any more code, or your understanding of how your code is supposed to work is wrong. Both paths lead to a better spot than without … Continue reading →

Posted in TDD | 9 Comments