Sign in with Facebook
Clean Code Quotes
Clean Code: A Handbook of Agile Software Craftsmanship
by
Robert C. Martin3 ratings, 4.33 average rating, 0 reviews
Open Preview
Clean Code Quotes
Showing 1-1 of 1
“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.
... Indeed, the ratio of time spent reading [code] vs. writing [code] is well over 10:1. We are constantly reading old code as part of the effort to write new code.
Because this ratio is so high, we want the reading of code to be easy, even if it makes the writing harder. Of course there’s no way to write code without reading it, so making it easy to read actually makes it easier to write.
When people look under the hood, we want them to be impressed with the neatness, consistency, and attention to detail that they perceive. We want them to be struck by the orderliness. We want their eyebrows to rise as they scroll through the modules. We want them to perceive that professionals have been at work. If instead they see a scrambled mass of code that looks like it was written by a bevy of drunken sailors, then they are likely to conclude that the same inattention to detail pervades every other aspect of the project.”
― Clean Code: A Handbook of Agile Software Craftsmanship
... Indeed, the ratio of time spent reading [code] vs. writing [code] is well over 10:1. We are constantly reading old code as part of the effort to write new code.
Because this ratio is so high, we want the reading of code to be easy, even if it makes the writing harder. Of course there’s no way to write code without reading it, so making it easy to read actually makes it easier to write.
When people look under the hood, we want them to be impressed with the neatness, consistency, and attention to detail that they perceive. We want them to be struck by the orderliness. We want their eyebrows to rise as they scroll through the modules. We want them to perceive that professionals have been at work. If instead they see a scrambled mass of code that looks like it was written by a bevy of drunken sailors, then they are likely to conclude that the same inattention to detail pervades every other aspect of the project.”
― Clean Code: A Handbook of Agile Software Craftsmanship
