🏷️ Naming is so important and so cumbersome in programming as Phil Carlton coined in his famous cite:
"There are only two hard things in Computer Science: cache invalidation and naming things."
📐From the design phase.
Having a common name glossary is the central point in methodologies like #DDD.
But even if you don´t follow it, you will appreciate having a ubiquitous language to communicate with all the people involved.
🚧 In the architect's hands naming is the core of its work.
Using #patterns is given name to proven solutions.
Defining #layers and tiers forces you to give them a name.
🏗️ When coding you are writing the user #stories in a formal and precise language.
But this language is scarce in words.
Only the basic constructs for creating modules, functions, classes, data structures, and a few control flow instructions.
👷 Everything else is your responsibility.
You are writing stories in your own language.
Yes, you create the language in what you write.
Naming your variables and your functions is like establishing nouns and verbs for a new language; a language adapted to the business domain.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
🏷️ Naming is so important and so cumbersome in programming as Phil Karlton coined in his famous cite:
"There are only two hard things in Computer Science: cache invalidation and naming things."
A thread 🧵👇
📐From the design phase.
Having a common name glossary is the central point in methodologies like #DDD.
But even if you don´t follow it, you will appreciate having a #ubiquitous language to communicate with all the people involved.
🚧 In the architect's hands naming is the core of its work.
Creating #patterns is given a name to proven solutions. Using them is using those names.
Dividing codebases and defining #layers and #tiers forces you to give them a name.