Product Description

Widely considered one of the best practical guides to programming, Steve McConnell’s original CODE COMPLETE has been helping developers write better software for more than a decade. Now this classic book has been fully updated and revised with leading-edge practices—and hundreds of new code samples—illustrating the art and science of software construction. Capturing the body of knowledge available from research, academia, and everyday commercial practice, McConnell synthesizes the most effective techniques and must-know principles into clear, pragmatic guidance. No matter what your experience level, development environment, or project size, this book will inform and stimulate your thinking—and help you build the highest quality code. Discover the timeless techniques and strategies that help you: •Design for minimum complexity and maximum creativity •Reap the benefits of collaborative development •Apply defensive programming techniques to reduce and flush out errors •Exploit opportunities to refactor—or evolve—code, and do it safely •Use construction practices that are right-weight for your project •Debug problems quickly and effectively •Resolve critical construction issues early and correctly •Build quality into the beginning, middle, and end of your project 

Product Details

• Amazon Sales Rank: #3167 in Books
• Brand: Microsoft
• Published on: 2004-07-01
• Format: Unabridged
• Original language: English
• Number of items: 1
• Binding: Paperback
• 960 pages

Customer Reviews

Mandatory
Code Complete 2 is another brilliant book from Steve mcConnell. I should have read this years ago when I graduated. It is easy to read despite being fairly chunky. Everything is here you'll need. Designing classes, loops, naming conventions, debugging, testing, refactoring, human factors and loads loads more.

I agree in part with the more negative review on here. Any book is the authors point of view, but Steve mcConnell backs everything he says with data from previous experiments, journals and "famous" successfull/failed projects. There are many compelling arguments in here to change the processes you use to develop and design software. I'm getting my boss to get everyone in the department a copy before our next major project. It's that good!

This needs to be mandatory reading, no excuses.

Essential Reading for Professional Software Developers
Every professional developer should read this book at least once in their career. It covers almost every aspect of modern software development (from a professional programmers point of view). In particular it adds some perspective to the many competing development methodologies around today. It's also relevant to both lone developers and those working in larger teams.

There's a few odd ommissions e.g. no coverage UML or patterns. However this is "nit picking" as the book as it stands (all 800+ pages) is a worldwind tour 'd force of best proctices within the software development industry.

Oh, and it's also a great read.

Highly recommended for beginners but not necessarily for veterans!
A very well-written, seminal book on software construction. It very effectively covers almost all of the important topics in software construction. This book partly also served as a revision of my software engineering classes in university. It very effectively, in fact blatantly reminds us that software engineering is all about managing complexity. However at the same time I have to be honest also in that it is not as "must have" as it is often projected. It also comes from the fact that for someone with 3-4+ years of professional experience, this book is not going to offer that much (though still recommended). With some 3.5 years working in industry, I already knew roughly some 70% of things told in this book. For example all those chapters on coding and naming conventions are not going to offer you much if you haven't already learned these things in first few years of your career. Many practices this book recommends are too good that are too obvious and many practices it condemns are too bad that make me wonder if people are really using them. Some chapters are really awesome, like "Design in Construction" and "Working Classes", some are very good such as "Managing Construction", most of them are good such as "Using Conditional" and "Unusual Control Structures", and a few are so so, e.g. "Layout and Style" , "Refactoring". Another problem with this book is that it is unnecessarily long, and verbose. It is composed of 35 chapters. In places it feels too redundant. In my opinion, the size of the book could have cut down by fixing these redundant things. e.g. why to include chapter 34, and why those Checklist sections? Also note that this book is more about coding than programming, e.g., it does not even remotely discuss data structures or algorithm analysis (Big O and stuff) etc.

Summary: Highly recommended to beginners in professional software development, moderately recommended to people with some experience, and not necessarily recommended to veterans.