Clean Code Quotes

“is not the language that makes programs appear simple. It is the programmer that make the language appear simple!”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“The hardest thing about choosing good names is that it requires good descriptive skills and a shared cultural background. This is a teaching issue rather than a technical, business, or
management issue.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“it’s confusing to have a controller and a manager and a driver in the same
code base. What is the essential difference between a DeviceManager and a Protocol-Controller? Why are both not controllers or both not managers? Are they both Drivers really? The name leads you to expect two objects that have very different type as well as
having different classes.

A consistent lexicon is a great boon to the programmers who must use your code.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Cuteness in code often appears in the form of colloquialisms or slang. For example, don’t use the name whack() to mean kill(). Don’t tell little culture-dependent jokes like eatMyShorts() to mean abort().
Say what you mean. Mean what you say.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“The problem isn’t the simplicity of the code but the implicity of the code (to coin a phrase): the degree to which the context is not explicit in the code itself.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Whether you are designing systems or individual modules, never forget to use the simplest thing that can possibly work.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Who can justify the expense of a six-lane highway through the middle of a small town that anticipates growth? Who would want such a road through their town?”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“More precisely, the Law of Demeter says that a method f of a class C should only call the methods of these: • C • An object created by f • An object passed as an argument to f • An object held in an instance variable of C”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Objects hide their data behind abstractions and expose functions that operate on that data. Data structure expose their data and have no meaningful functions.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Dependent Functions. If one function calls another, they should be vertically close, and the caller should be above the callee, if at all possible.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“But then closely related concepts should not be separated into different files unless you have a very good reason. Indeed, this is one of the reasons that protected variables should be avoided.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“The topmost parts of the source file should provide the high-level concepts and algorithms. Detail should increase as we move downward, until at the end we find the lowest level functions and details in the source file.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“You should choose a set of simple rules that govern the format of your code, and then you should consistently apply those rules. If you are working on a team, then the team should agree to a single set of formatting rules and all members should comply.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Duplication may be the root of all evil in software. Many principles and practices have been created for the purpose of controlling or eliminating it.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Ward’s principle: “You know you are working on clean code when each routine turns out to be pretty much what you expected.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Leave the campground cleaner than you found it.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Duplication and expressiveness take me a very long way into what I consider clean code, and improving dirty code with just these two things in mind can make a huge difference. There is, however, one other thing that I’m aware of doing, which is a bit harder to explain.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship