Å·±¦ÓéÀÖ

“Truth can only be found in one place: the code.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Indeed, the ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code. ...[Therefore,] making it easy to read makes it easier to write.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“It is not enough for code to work.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“So if you want to go fast, if you want to get done quickly, if you want your code to be easy to write, make it easy to read.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“You should name a variable using the same care with which you name a first-born child.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“A long descriptive name is better than a short enigmatic name. A long descriptive name is better than a long descriptive comment.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Clean code always looks like it was written by someone who cares.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Of course bad code can be cleaned up. But it’s very expensive.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Clean code is not written by following a set of rules. You don’t become a software craftsman by learning a list of heuristics. Professionalism and craftsmanship come from values that drive disciplines.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“It 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

“Redundant comments are just places to collect lies and misinformation.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“You are reading this book for two reasons. First, you are a programmer. Second, you want to be a better programmer. Good. We need better programmers.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“There are two parts to learning craftsmanship: knowledge and work. You must gain the knowledge of principles, patterns, practices, and heuristics that a craftsman knows, and you must also grind that knowledge into your fingers, eyes, and gut by working hard and
practicing.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“One difference between a smart programmer and a professional programmer is that
the professional understands that clarity is king. Professionals use their powers for good and write code that others can understand.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Don’t Use a Comment When You Can Use a Function or a Variable”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Programmers must avoid leaving false clues that obscure the meaning of code.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Perhaps you thought that “getting it workingâ€� was the first order of business for a professional developer. I hope by now, however, that this book has disabused you of that idea. The functionality that you create today has a good chance of changing in the next release, but the readability of your code will have a profound effect on all the changes that will ever be made.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“The proper use of comments is to compensate for our failure to express ourself in code. Note that I used the word failure. I meant it. Comments are always failures.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Honesty in small things is not a small thing.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“The first rule of functions is that they should be small. The second rule of functions is that they should be smaller than that.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“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.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“When you see commented-out code, delete it!”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“FUNCTIONS SHOULD DO ONE THING. THEY SHOULD DO IT WELL. THEY SHOULD DO IT ONLY.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Duplication is the primary enemy of a well-designed system. It represents additional work, additional risk, and additional unnecessary complexity.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“First Law You may not write production code until you have written a failing unit test. Second Law You may not write more of a unit test than is sufficient to fail, and not compiling is failing. Third Law You may not write more production code than is sufficient to pass the currently failing test.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“Whatever else a TODO might be, it is not an excuse to leave bad code in the system.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“SRP is one of the more important concept in OO design. It’s also one of the simpler concepts to understand and adhere to. Yet oddly, SRP is often the most abused class design principle.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“A long descriptive name is better than a long descriptive comment.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“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 author of Object
Oriented Analysis and Design with
Applications”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“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 performance
close to optimal so as not to tempt
people to make the code messy with unprincipled optimizations. Clean code does one thing well.

-Bjarne Stroustrup, inventor of C++
and author of The C++ Programming
Language”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship