...
Names build images and advance expectations. They make how we look at the entities they define, how we assume to handle them and expect their behavior behaviour in response to our actions.
...
Naming things raises above the source code level and goes deeper than just maintenance issues. It is also about the scope of the project. If you cannot define the scope of the project, name the central pieces, it is like a 19th century map with a lot of white spots.
Source: Wikipedia
The white spots are discomforting. One does not know what’s inside. It’s a source of danger. Catographers Cartographers depicted such uncertainty with the phrase “Here be dragons“. So it is hard to comprehend the target and scope of the whole venture. Every white area is a risk for the team to misunderstand something or make something up that is not true at all.
Source: Wikipedia
Killer Joke Pattern
...
