Series Clean Code - Overview (Part 1)

Today, I'll talk about Clean Code handbook. This is a great handbook and almost programmers should read and practice to become a better programmer. Because the content is long, I'll divide this topic into 2 parts:  
  • Part 1: Introduce about Clean Code handbook and some main topics which I'll talk about.  
  • Part 2: Talk about that main chapter details.

But before we start, I would like to mention 3 questions for you first:
1/ What is software construction?
2/ What is a good software code?
3/ How to write code better?

What is software construction?

  • It is a field of software engineering.
  • It creates meaningful software through combination of programming, verification, unit testing, integration testing, and debugging.
  • Linking all areas of software engineering varies, mostly in software design and software testing. 
What is a good software code?

  • Good job 
  • Easy reading 
  • Able to testing 
  • Easy to maintain 
  • Feel comfortable when look at 
  • Easy to change
  • Simple
  • Effective
How to write code better?
As I told you about software construction and software code like above. You can see that the software construction quality is evaluated through good software code. So, how to write code better?

Clean Code - A Handbook of Agile Software Craftsmanship is a solution for us. This handbook is written by the following Object Mentors:
  • Robert C. Martin
  • Michael C. Feathers Timothy R. Ottinger
  • Jeffrey J. Langr Brett L. Schuchert
  • James W. Grenning Kevin Dean Wampler
  • Object Mentor Inc. 
And a extremely impress slogan at the cover of this handbook:
"Writing clean code is what you must do in order to call yourself a professional. 
There is no reasonable excuse for doing anything less than your best."
 
The content of the book that I will mention
Because this handbook has many interest things and I couldn't say all content of it. So, I just select some interest topics I like most to say:

  • There will be code
  • Bad code
  • The total cost of owning a Mess
  • Schools of thought
  • We are authors
  • The boy scout rule
  • Prequel and principles
 2 reasons to read this book:
  • First, you are a programmer. 
  • Second, you want to be a better programmer.
We will look at the code in many different directions:
  • Look at the code from start to finish. 
  • Look at the code from the bottom up.
  • Review code follow code blocks from inside out.
When we do that we will:
  • Understand a lot about the code. 
  • Know there is a difference between good code and bad code. 
  • Know how to write good code. 
  • Know how to turn bad code into good code. 
 And I will talk about the above topics in part 2. 

0 nhận xét:

Đăng nhận xét

Được tạo bởi Blogger.