This article is about the second group of concepts I wanted to talk about after re-reading Clean Architecture.
I want to try something different this time: Instead of elaborating each idea in long, continuous prose, I'll just list them as separate chunks.
So, here it goes:
I recently started re-reading Bob Martin's Clean Architecture and found two other ideas I wanted to share. One of them (the topic of this article) is the dual nature of the way software developers provide value through code.
When you implement (or modify) a feature in your system you are
This article is a summary of what I consider to be the most important concepts of the book Domain-Driven Design, by Eric Evans. I tried to condense the most important ideas in a single article for anyone interested in the topic. I attempted to pack in as much information as
Depend on behavior, not on data
This is one of the most powerful pieces of advice in OO programming I've ever received.
It means that objects shouldn't be seen just as a collection of data structures. Instead, you should visualize them as software entities that can respond to messages and
In a previous article, we talked about the importance of comments in software development.
Even though they are powerful tools for improving the readability of our code, we should use them with care. A good comment can make the code easier to understand, but a bad one can harm your