Writing code that any programmer who read can understand is a must-have skill for software developers. The fact is: only 20% of the programmers have the ability.
“Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” — Martin Fowler
When I started caring about code readability I noticed that my code started to be:
- easier to maintain
- easier to refactor
Robert “Uncle Bob” Martin’s “Clean Code: A Handbook of Agile Software Craftsmanship” is the clean coder programmer bible. This book talks about code, behaviour, automated tests and so on.
Let’s get practical! Writing meaningful names.
One of Clean Code chapters talks about meaningful naming. In this story, you are going to be the code reader. Take a look at this function:
def calc(n1, n2)
return n1 / n2
Do you think “calc” is a good name for this function? Uncle Bob would say: no! Why?
- “calc” is an abbreviation: don’t!
- Functions do something. It must be named with a verb.
- Even I rename “calc” to “calculate”, it still be vague. We need to improve the semantics by giving the function name more meaning.
This function divides two numbers. “divide” is a good name for it.
def divide(n1, n2)
return n1 / n2
result = divide(1, 2)
We still have problems with it. “n1” and “n2”, the parameters, are not semantic. What if we call them “dividend” and “divisor”? The same thing to the “result” variable. It should be called something like “quotient”.
def divide(dividend, divisor)
return dividend / divisor
quotient = divide(1, 2)
Much more semantic!
If you are not convinced to read this book yet, take a look in this picture and buy this must-read book!
The Book Every Programmer Should Read was originally published in Hacker Noon on Medium, where people are continuing the conversation by highlighting and responding to this story.
Posted by Vinicius Brasil on February 10, 2018 @ https://hackernoon.com/the-book-every-programmer-should-read-33b5ef2e532a?source=rss—-3a8144eabfe3—4