Clean Code: A Handbook of Agile Software Craftsmanship (Robert C. Martin Series)
Rate it:
Open Preview
3%
Flag icon
A place for everything, and everything in its place.
4%
Flag icon
You should name a variable using the same care with which you name a first-born child.
5%
Flag icon
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.
6%
Flag icon
A building with broken windows looks like nobody cares about it. So other people stop caring. They allow more windows to become broken.
9%
Flag icon
programming is a social activity.
10%
Flag icon
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.
12%
Flag icon
The first rule of functions is that they should be small. The second rule of functions is that they should be smaller than that.
12%
Flag icon
FUNCTIONS SHOULD DO ONE THING. THEY SHOULD DO IT WELL. THEY SHOULD DO IT ONLY.
14%
Flag icon
Side effects are lies.
15%
Flag icon
This side effect creates a temporal coupling. That is, checkPassword can only be called at certain times
16%
Flag icon
11. Those who felt that they could get away without recompiling and redeploying have been found—and dealt with.
21%
Flag icon
Others who see that commented-out code won’t have the courage to delete it. They’ll think it is there for a reason and is too important to delete. So commented-out code gathers like dregs at the bottom of a bad bottle of wine.
22%
Flag icon
Code formatting is important. It is too important to ignore and it is too important to treat religiously.
22%
Flag icon
communication is the professional developer’s first order of business. Perhaps you thought that “getting it working” was the first order of business for a professional developer.