My notes from chapter 1 of "Clean Code"

Follow up of My notes from the introduction of “Clean Code”

Notes

There Will Be Code

“Code is the language in which we ultimately express the requirements”

-> “There Will Be Code”

Page: 2

Bad Code

A company behind a killer app went out of business as a result of bad code.

Page: 2

The Total Cost of Owning a Mess

The consequences of messy code can be significant.

The productivity of the team will decrease and eventually approach zero.

Page: 4

The Grand Redesign in the Sky

Redesigns aren’t the solution to messy code.

Page: 5

Attitude

Messy code is our own fault. Not the requirements, schedule, management or marketing types. They rely on us for the information they need to make promises and commitments.

Page: 5

The Primal Conundrum

Keep the code as clean as possible to go fast.

Page: 6

The Art of Clean Code

Being able to recognize clean code from dirty code does not mean that we know how to write clean code.

Writing clean code requires the disciplined use of techniques applied through a carefully obtained sense of “cleanliness”.

Page: 6

Please buy this book if you want know more about the above notes. These notes only serve as a quick reference to important information in the book. If these notes are too insightfull and in conflict with the copyright, please get in touch with me.