Cristian > Cristian's Quotes

“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

“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 always looks like it was written by someone who cares.”
― Robert C. Martin, Clean Code: A Handbook of Agile Software Craftsmanship

“The only way to go fast, is to go well.”
― Robert C. Martin, Clean Architecture

“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

“The problem is that we view estimates in different ways. Business likes to view estimates as commitments. Developers like to view estimates as guesses. The difference is profound.”
― Robert C. Martin, Clean Coder, The: A Code of Conduct for Professional Programmers

“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

“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

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

“Dijkstra once said, “Testing shows the presence, not the absence, of bugs.” In other words, a program can be proven incorrect by a test, but it cannot be proven correct. All that tests can do, after sufficient testing effort, is allow us to deem a program to be correct enough for our purposes.”
― Robert C. Martin, Clean Architecture: A Craftsman's Guide to Software Structure and Design

“You see, programmers tend to be arrogant, self-absorbed introverts. We didn’t get into this business because we like people.”
― Robert C. Martin, Clean Coder, The: A Code of Conduct for Professional Programmers

“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

“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

“Building a project should be a single trivial operation.”
― 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

“When you cannot concentrate and focus sufficiently, the code you write will be wrong. It will have bugs. It will have the wrong structure. It will be opaque and convoluted. It will not solve the customers’ real problems. In short, it will have to be reworked or redone. Working while distracted creates waste.”
― Robert C. Martin, Clean Coder, The: A Code of Conduct for Professional Programmers

“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

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