This post is about a better implementation of Value Object.
In this post, I’d like to talk about what I think is one of the most damaging attitudes a company or a person can have in the field of software development: short-sighted perspective.
I’m back to the regular posting schedule. No more game development, at least for now.
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.