A couple of days ago I had a conversation with a friend who is learning to program.
We were talking about the difficulty of remembering what each concept means and what every keyword does. The conversation eventually led to this question:
Ok, but when will I stop needing the docs?
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
Hello there,
I recently started working on a couple of side projects that require a bit more attention and time than I expected, so I decided to put the article schedule on hold for a while so that I can focus on finishing them.
I expect to be back with