• Mechanical approach to domain modeling - In this post, I’d like to talk about a mechanical approach to domain modeling. It sometimes arises when teams start applying Domain-Driven Design (DDD) principles to their projects and when they don’t have enough experience with it yet. [Enterprise Craftsmanship]

Permalink | From 29 February 2016 to 06 March 2016 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

• Partially initialized entities anti-pattern - The topic described in this article is a part of my Domain-Driven Design in Practice Pluralsight course. In this post, I’d like to talk about the partially initialized entities anti-pattern: anti-pattern that is often used in conjunction with repositories. Partially initialized entities Partially initialized entities are entities which are not fully constructed and returned as a result of some operation, usually an operation of fetching them from the database. [Enterprise Craftsmanship]
• Type Safety and Money - Below is an attempt at illustrating a design/redesign process I went through at a client, who’s started refactoring the core systems their business depends on. Design is the part of software development that is the most messy, the hardest to fit into rules or well-defined processes. In fact, while writing this post, I tweeted: “There are surprisingly few software design books that recommend taking a walk, a shower, or a nap, as an important step. ” None of the solutions offered below should be taken as truth. I may have already changed my mind on some of them by the time you read them. History In 2010, I wrote a small library with some Value Objects to represent money, and in 2011, I published a first version. [Mathias Verraes]

Permalink | From 22 February 2016 to 28 February 2016 | Last updated on: Mon, 7 Jun 2021 09:18:52 GMT

• 3 ways of achieving code correctness - Code correctness verification is not an easy task. At the same time, it’s one of the most important problems we have when we build software projects. In this article, I’ll compare 3 different ways of achieving code correctness. [Enterprise Craftsmanship]

Permalink | From 15 February 2016 to 21 February 2016 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

• Specification pattern: C# implementation - The topic described in this article is a part of my Specification Pattern in C# Pluralsight course. Specification pattern is not a new topic, there are many of its implementations on the Internet already. In this post, I’d like to discuss the use cases for the pattern and compare several common implementations to each other. 1. Specification pattern: what’s that? Specification pattern is a pattern that allows us to encapsulate some piece of domain knowledge into a single unit - specification - and reuse it in different parts of the code base. [Enterprise Craftsmanship]

Permalink | From 08 February 2016 to 14 February 2016 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT

• Classes internal to an aggregate: entities or value objects? - While such classes as Person and Money are pretty intuitive and can be easily attributed to either entities or value objects, the choice isn’t so obvious when it comes to classes that are internal to an aggregate. That is classes that aren’t roots of their own aggregates but rather parts of existing ones. [Enterprise Craftsmanship]

Permalink | From 01 February 2016 to 07 February 2016 | Last updated on: Mon, 7 Jun 2021 09:11:14 GMT