Clean Coder, The: A Code of Conduct for Professional Programmers (Robert C. Martin Series)

by Robert C. Martin

“pressure makes diamonds.”

This book will tell step by step exactly how to present yourself and interact as a professional.

But that responsibility includes one other thing—one frightening thing. As an engineer, you have a depth of knowledge about your systems and projects that no managers can possibly have. With that knowledge comes the responsibility to act.

Software is too complex to create without bugs.

you must be responsible for your imperfections.

the first thing you must practice is apologizing.

Releasing code to QA that you don’t know works is unprofessional.

How much of the code should be tested with these automated unit tests? Do I really need to answer that question? All of it! All. Of. It.

It is the structure of your code that allows it to be flexible.

The fundamental assumption underlying all software projects is that software is easy to change. If you violate this assumption by creating inflexible structures, then you undercut the economic model that the entire industry is based on.

You must be able to make changes without exorbitant costs.

If you want your software to be flexible, you have to flex it!

It is also not your employer’s responsibility to give you the time you need to learn. Some employers may provide that time. Some employers may even demand that you take the time.

You should plan on working 60 hours per week. The first 40 are for your employer. The remaining 20 are for you. During this remaining 20 hours you should be reading, practicing, learning, and otherwise enhancing your career.

Perhaps you don’t want to make that kind of commitment. That’s fine, but you should not then think of yourself as a professional. Professionals spend time caring for their profession.

It is the responsibility of every software professional to understand the domain of the solutions they are programming.

Your employer’s problems are your problems.

The client will always extend the deadline. They will always want more features. They will always want change—LATE.

If you are tired or distracted, do not code.

Pairing can be very helpful as a way to deal with interruptions.

Software development is a marathon, not a sprint.

A marathon runner takes care of her body both before and during the race. Professional programmers conserve their energy and creativity with the same care.

Programming is an intellectual exercise that requires extended periods of concentration and focus. Focus is a scarce resource, rather like manna.1 After you have expended your focus-manna, you have to recharge by doing unfocused activities for an hour or more.