What is clean code?

This question should have so many answers if you ask it to different people. For example in the Clean Code book, there are so many answers in the first chapter, and some of them are:

•  “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)
• “You know you are working on clean code when each routine you read turns out to be pretty much what you expected. You can call it beautiful code when the code also makes it look like the language was made for the problem”( Ward Cunningham)

     For me what is clean code is not an easy answer. After start reading Clean Code book, right now I understand that clean code is more than just a program that runs correctly. Clean code is a code that you can read as it was a history, that has meaningful names in variables, classes, methods. Also clean code is code that is well structured, that does not have any duplication.

     Moreover clean code is code where classes and methods are small and explain what they do in its easiest form without any comment. But, for me also after been here in Pernix, I’ve learned that clean code also have tests, where there are a really important thing to make a great application. Clean code is also efficient, focused, and people are not afraid to modify it.  On the other hand, I can tell that clean code also is about to use right the principles and patterns that exist. Because in the end, that is why patterns and principles exist; applying all these things together make clean code.

Bibliography

Martin, R. C. (2009). Clean Code. Prentice Hall.