Robert Martin

The Robert C. Martin Clean Code Collection (Collection)

Notify me when the book’s added
To read this book, upload an EPUB or FB2 file to Bookmate. How do I upload a book?
  • b4777467766has quotedlast year
    If a name requires a comment, then the name does not reveal its intent.
  • b4777467766has quotedlast year
    Choosing good names takes time but saves more than it takes.
  • b4777467766has quotedlast year
    the ratio of time spent reading vs. writing 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.
  • b4777467766has quotedlast year
    The @author field of a Javadoc tells us who we are. We are authors. And one thing about authors is that they have readers. Indeed, authors are responsible for communicating well with their readers.
  • b4777467766has quotedlast year
    One word: care. That’s really the topic of this book.
  • b4777467766has quotedlast year
    Most of us know when a picture is painted well or badly. But being able to recognize good art from bad does not mean that we know how to paint. So too being able to recognize clean code from dirty code does not mean that we know how to write clean code!
  • b4777467766has quotedlast year
    it is unprofessional for programmers to bend to the will of managers who don’t understand the risks of making messes.
  • b4777467766has quotedlast year
    The managers and marketers look to us for the information they need to make promises and commitments; and even when they don’t look to us, we should not be shy about telling them what we think. The users look to us to validate the way the requirements will fit into the system. The project managers look to us to help work out the schedule. We are deeply complicit in the planning of the project and share a great deal of the responsibility for any failures; especially if those failures have to do with bad code!
  • b4777467766has quotedlast year
    Most managers want good code, even when they are obsessing about the schedule. They may defend the schedule and requirements with passion; but that’s their job. It’s your job to defend the code with equal passion.
  • b4777467766has quotedlast year
    This race can go on for a very long time. I’ve seen it take 10 years. And by the time it’s done, the original members of the tiger team are long gone, and the current members are demanding that the new system be redesigned because it’s such a mess.
fb2epub
Drag & drop your files (not more than 5 at once)