Part 2 of my story. You can read the first part here.
If you read this blog regularly, you know that I usually write about DDD, functional programming, and enterprise software development best practices in general. These are the techniques I enjoy talking about, as well as applying them in my own projects. However, there was another field I always wanted to try myself in. That is game development. The ability to write my own games was the reason why I started learning to program in the first place. And I believe many programmers had this motivation behind their careers as well.
But let’s start from the beginning.
This post is about how to work with information that is spread across multiple microservices.
In this post, we’ll discuss Value Objects. Specifically, when to introduce them into your code.
In this post, I’d like to talk about naming and Ubiquitous Language.
I apologize to everyone who’s waiting for my response to their code review requests. I was busy dealing with some personal stuff the last couple of weeks. Moving forward, I’m going to maintain a one post a week schedule where “regular” articles would take turns with code reviews. This article is a regular one, so the one next week would be a code review.
Today, I’d like to talk about IEnumerable and IReadOnlyList collection interfaces. We’ll discuss which of them is preferable and in what circumstance.
In this post, we will explore a common design problem: implementing a Main Something property. There’s an equally common solution to this problem which is sub-optimal in most cases.