This is a very hefty book. With over 800 pages it covers a lot of ground on software construction. The author give very detailed coverage to all ways to make your code lucid. He points out that software is read many more times than it is written, so well written clear code can have significant impact on productivity.
One of the things I appreciated about the book is the way it uses other research. Instead of degenerating into someone's ranting opinions, the book cites numerous studies and research to support claims and suggested methods. In some places the author states his personal preferences while noting that studies indicate no noticable advantage over other methods.
The book talks a lot about programming in a way that hides complexity. excellent programming isn't trying to keep track of hundreds of classes and variables and finally getting the software to compile. excellent programming is designing and coding in a way that allows you to focus on only one small part of the program at a time.
Clear, Concise, Easy to understand. The Holy Grail of programming references. A must-read for professional programmers.
Code Complete by Steve McConnell is the convergence (the crossroads) of experience, research, and theory. This book is invaluable, the Holy Grail of programming reference books. McConnell's writing style is clear, concise, easy to understand and often humorous.
Programmers on every level (from introduction to master) will benefit from reading this book. Programmers at the introduction level may find some topics advanced, but references to additional resources are close at hand. This book covers a broad range of interconnected topics ranging from: variable names, code-tuning, personal character, managing your manager, gonzo programming and much more. The emphasis is always on successful software design techniques.
McConnell doesn't shy away from presenting hard data and details; he nails the "whys" that so many other texts avoid.
Selected quotes from Code Complete:
"People have already made all the mistakes that you're making now, and unless you're a glutton for punishment, you'll prefer reading their books and avoiding their mistakes to inventing new versions of old problems." (Chapter 35)
"Once a programmer realizes that programming principles transcend the syntax of any specific language, the doors swing open to knowledge that truly makes a difference in quality and productivity." (Preface)
"The value of hands-on experience as compared to book learning is smaller in software development than in many other fields" (Chapter 35)
It's interesting to note that Code Complete is a required read to become a practitioner (intermediate) level employee in McConnell's company (Construx).
Code Complete is often compared with The Pragmatic Programmer: From Journeyman to Master [Hunt, Andrew, and Thomas, David]; the topics covered in the Pragmatic Programmer are a small subset of Code Complete. Code Complete is consistently written at a higher level, and offers more references for continual research and professional development. But don't take my word for it; read both, the Pragmatic Programmer makes a good prerequisite to Code Complete.
Hailing this book as "The Holy Grail of programming references" may seem fanatical, but I have yet to find a book that remotely measures up to Code Complete.
Build software - dont write it...
Absolute must-read for the developer turned manager! My recommendation is that you glean a summary of your favorite excerpts and share them with your whole team.
Writing smarter code
The book is what I was looking for. It describes how do construct a smart program. The focus is on construction and not on design so there is only a short overview of good design although they tell you 1000 times to take more time in designing than in coding.
But a very good book anyway.