Clean Code by Uncle Bob

Let’s dive into together Clean Code : Handbook of Agile Software Craftsmanship book. This article includes first chapter of the book.

Chapter 1 ( Clean Code)

In this chapter, you can see many views by expert programmer about clean code principle. All of them emphasize importance of clean code. Why it is so important ?

Programmers spend a lot of time writing code. So, what happens if the code they write is not clean? Most likely, they will have to spend time on the same code again to refactor it. This process causes loss of time and cost. On the other hand, As time goes by, our projects develop and we need to add many new features. However, during this growth process, bad codes in the project may create errors and cause the project to come to a halt.

The Total Cost of Owning a Mess

• Messy code kills the productivity by the time.
• It causes redesign all code again.
• It makes it difficult for the new team member to contribute to the project.

Quotes from well-known programmers

“Clean code is simple and direct. Clean code reads like well-written prose. Clean code never obscures the designer’s intent but rather is full of crisp abstractions and straightforward lines of control.”

Grady Booch

“I like my code to be elegant and efficient. The logic should be straightforward to make it hard for bugs to hide, the dependencies minimal to ease maintenance, error handling complete according to an articulated strategy, and per- formance close to optimal so as not to tempt people to make the code messy with unprinci- pled optimizations. Clean code does one thing well.”

Bjarne Stroustrup

Conclusion

If you want to be better programmer, you need to understand many principles and approaches. I think, clean code is the most important principle in software area. Regardless of the developer’s level, it is the principle that must be learned and implemented first. Thank you for reading :)