DeepRead
Cover of Clean Code

About the book

A practical guide to writing readable, maintainable software at the level of individual names, functions, classes, comments, and tests. It draws its examples mostly from Java and includes extended refactoring case studies that walk through improving real code step by step. Messy code is expensive because it slows every later change, so writing clean code is a professional responsibility rather than a matter of taste. Clean code is code whose intent is obvious: names that say what things are, short functions that do one thing, and comments only where the code cannot say the same thing itself. The book also holds that tests should be kept as clean as production code and that a collection of heuristics and code smells can be used to judge and improve a codebase.

Written by Claude from what it knows of this book.

What Hacker News says 40% recommend · 29% critical

010020020082015202020262021 peak · 121
This bookAverage book in Software design and clean code

In the commenters’ own words

What Open Library readers say 4.40 from 48 ratings

  1. 526
  2. 415
  3. 37
  4. 20
  5. 10
  • 893 want to read
  • 37 reading
  • 68 have read

Open Library’s page for the book

What critics say, via Wikipedia

No Wikipedia article about this book yet, so no critics to quote.

Reddit communities — coming later

The threads it came up in

Details

First published
2008
ISBN
9780132350884
Editions known
24 at Open Library
Open Library
OL17618370W

Agile software developmentCoding theoryComputer softwareComputer software, developmentReliability

Explore in the mosaic

Read next: its neighbours on the mosaic