Before you go, check out these stories!
0
Never email CSV templates againThe Book Every Programmer Should Read by@vnbrsThe Book Every Programmer Should Read
February 8th 2018 53,836 reads
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
- reusable
- consistent
The Book
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
end
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
end
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
end
quotient = divide(1, 2)
Much more semantic!
Thank you for reading! Don't forget to follow me on Medium, Instagram and LinkedIn.
Related
Tags
Subscribe to get your daily round-up of top tech stories!