3 things that will make or break your project

This article is about 3 things that can make or break any software project.

Assertion messages in tests

In this post, we’ll talk about whether or not you should use assertion messages in tests.

Is Entity the same as Value Object?

In this post, we’ll discuss an interesting question about whether the concepts of Entity and Value Object are the same.

DDD and bulk operations

Combining bulk operations with Domain-Driven Design is a tough problem. In this article, we’ll look at why that is so and discuss ways to marry the two.

Combining ASP.NET Core validation attributes with Value Objects

This is a continuation of the article series about some more advanced error handling techniques.

Advanced error handling techniques

This post describes some (more) advanced error handling techniques. I’ll probably do a series because this topic is large and there’s quite a few things that need to be cleared out, but we’ll see.

You are naming your tests wrong!

Giving your tests expressive names is important. Proper naming helps understand what the test verifies and how the underlying system behaves. In this post, we’ll take a look at a popular, yet inferior naming convention and see how it can be improved.

I'm writing a book!

I’m writing a book called Unit Testing: Principles, Patterns and Practices.

Merging domain events before dispatching

This post describes a common problem: how to deal with multiple domain events if raising of one of them must negate the others.

CQRS and exception handling

In this article, I’d like to discuss one particular aspect of exception handling relevant to CQRS and the decorator pattern.