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 is a WIP, more words still need to be added. You'd be surprised by how rich and diverse programming jargon is, especially when we need to express simple ideas in complicated ways.
Agile: We don't do much planning here.
Bleeding Edge: I read about this new lib/framework on
CVs are weird things, and the older I get the harder it gets for me to understand them.
They say nothing about your capacity to persevere through big and small adversities.
They say nothing about your ability to communicate effectively and build bonds with other people.
They say little about
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