Have you ever felt like you’re missing something when doing some system component desing. When we read books and watch conferences everything is peachy, but somehow not in your case. You start doubting yourself it was so simple and now? Why the things I make seem to be somewhat skewed.
For a long time I shared that feeling. Trust me I understand you. It turned out that as always there was an error to be corrected. It was all about names..
Here are the most fatal mistakes I’ve made during all my years. I share them with you so you won’t have to! Please learn from my mistakes!
1. Naming too soon
The first and most often made mistake. We start the design sessions from naming components. WE KNOW what it is before we even begin. We slam the first thing that comes to our mind almost shouting: I won!
Shouldn’t we name it? After all, we need to define something. So yes, we need to give it a name, and no we shouldn’t do it. Giving some components a MEANINGFUL name from the start is not a good idea. This defines its scope and responsibilities IMPLICITLY. That means in everyone’s mind, without ever speaking them out loud. This is dangerous. Remember we are in this session to BUILD COMMON UNDERSTANDING, not to throw nouns and draw arrows.
Continue reading “7 Fatal Mistakes of Naming in System Component Design”