Clean Code in PythonComment 1. A long time ago, I used this summary of some key points that I made to study the book Clean Code. I hope it helps others. Note: this summary doesn't exclude the need to read the book. The code can be measured with either "good" or "bad" in the code review or by how many minutes it takes you to talk about it. A clean code should be elegant, efficient, readable, simple, without duplications, and well-written.
The basics of writing Clean Code
Martin ] 1 , that are supposed to summarize the main concepts presented in the book. Just gonna mention that all the advice comes not from guesses but experience as the author claims. Variable name should say what is being measured and the unit of measurement , e. It is always useful to add the context to the variable names, e. It is sometimes a good idea to extract even one-line-if-condition to a separate method , as one can give this method a more descriptive name. It is important to keep in mind the keywords specific to different areas of IT, and avoid using them when we mean them in a different context.
amazon books war and peace tolstoy
"Clean Code" Robert C. Martin
Code is clean if it can be understood easily — by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability. Great job! I've read Clean Code and this summary is very helpful and a quick reference do-not-forget list. Good read, in light speed! Really useful, thanks!