Member-only story
The Top 10 Design Mistakes Every Programmer Should Avoid
6. “Tell-don’t-ask”
“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” — Martin Fowler
One of the most covered subjects on software development is how to create clean code, or as Martin Fowler says, code that humans can understand.
Although extensive literature exists covering the subject, there is almost no single code base free from some kind of code smells.
In fact, after 10 years writing code in multiple projects, I haven’t seen a single codebase free from some of the most elementar design mistakes.
Poor coding practices lead to unintended complexity that turns the task of understanding the code more difficult. This challenge to understand the code intent creates more propensity for bugs and a growing cost in code maintenance.
Here are the top design mistakes every programmer should avoid immediately.
1. Use good naming conventions in your messages
There is nothing that screams more lack of care than using bad names. Virtually all developers understand the importance of good naming, however, when we go to messaging name conventions it seems they forget entirely…