Goodreads helps you keep track of books you want to read.
Start by marking “Code Complete” as Want to Read:
Code Complete
Enlarge cover
Rate this book
Clear rating
Open Preview

Code Complete

4.24 of 5 stars 4.24  ·  rating details  ·  4,539 ratings  ·  212 reviews
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 ...more
Paperback, 2nd Edition, 914 pages
Published June 19th 2004 by Microsoft Press (first published 1993)
more details... edit details

Friend Reviews

To see what your friends thought of this book, please sign up.

Reader Q&A

To ask other readers questions about Code Complete, please sign up.

Be the first to ask a question about Code Complete

The Pragmatic Programmer by Andrew HuntThe C Programming Language by Brian W. KernighanDesign Patterns by Erich GammaStructure and Interpretation of Computer Programs by Harold AbelsonCode Complete by Steve McConnell
Essential Programming Books
5th out of 112 books — 270 voters
The Pragmatic Programmer by Andrew HuntClean Code by Robert C. MartinCode Complete by Steve McConnellRefactoring by Martin FowlerWorking Effectively with Legacy Code by Michael C. Feathers
Software Craftsmanship
3rd out of 20 books — 68 voters

More lists with this book...

Community Reviews

(showing 1-30 of 3,000)
filter  |  sort: default (?)  |  rating details
Jon Fuller
Code Complete 2... A Review

One-liner: Read it. 3.5 stars

I came into this with super high expectations. Things I'd heard people say: "I make everyone on my team read this." or "Every developer should start with this book". So, I thought, "sweet, a great 'back to basics' book... I can't wait!". I read through this book with a host of colleagues all with quite different experience levels and in different areas of expertise.

It was the best of times. It was the worst of times.

Well... maybe not the wo
Erika RS
Code Complete is a massive work, so this summary is, necessarily, very high level. It is not a book that one can absorb completely in one reading, but one can absorb its high level themes (summarized nicely in the second to last chapter).

"Conquer Complexity". High quality code manages complexity. No one can think of all of the levels of abstraction needed to fully understand a program at once; just admit it and try to make your code less complex. Complexity can be managed at every level of the
Steve McConnell's Code Complete 2 is a classic piece of literature in Software Development. I joined a book club for reading this book, and the discussions along the way were some of the most valuable I've had. It was very rewarding to me to see many of the pieces of advice given reaffirming my own coding practices and the way things are done here at SEP, but I certainly took some new information away. One of the main lessons taught throughout the book is that code should be easy to understand. ...more
Vasily Fomin
May 28, 2011 Vasily Fomin rated it 5 of 5 stars  ·  review of another edition
Recommends it for: programmers, IT-professionals

После повторного прочтения данной книги окончательно убеждаюсь в том, что данная книга должны быть прочитана, как минимум раз, каждым развивающимся разработчиком, менеджером связанным с разработкой, и тем, кто так или иначе связан с областью разработки.

Мое мнение может быть предвзятым, так как на момент написания - это единственная книга по разработке, которую я прочитал, но могу сказать, что автору удалось пролить свет на разработку как таковую, и мне, как начинающему разработчику она очень пом

So it’s a #1 must read programming book according to this poll on StackOverflow. That raises quite some expectations, and if you ask me, the book doesn’t really meet them.

I mean, it doesn’t even feel like a proper programming book - it’s written in some “Easy way to quit smoking for dummies” style. Every idea is explained verbosely, then illustrated with some numeric stats, then with a 3D chart, then with some real-life anecdote, then with a reference to a 1973 paper, and finally reiterated in a
Steve McConnell's Code Complete is absolutely essential to every software developer. The lessons contained in Code Complete are based on solid, time-tested principles. The time spent reading Code Complete is time spent bettering your career as a developer.
Terribly bloated. Long-winded and trivial. I do not get the high score for this book; in a related area, but much more crisp is Programming Pearls (it even engages your brain, imagine that).
Yehuda Prizont
The bible of practical programming.
I bought the first edition, read about 400-500 pages and then the book was lost in a move. A few years later I got the second edition and read it again from the beginning and probably got to something like page 700. I then moved overseas and once again the book didn't make it across the ocean. Therefore, I have to include a small disclaimer that I didn't read the whole book. It is close to 1000 pages.
I don't remember any useless or impractical chapter. The book
Purchased this book as a textbook for a Software Engineering class at school. The teacher said he enjoyed it quite a bit and that we weren't going to reference it as much as he'd like (considering the other texts for the class). His comment piqued my interest. Upon finishing the first reading assignment I continued along to the next chapter. Like it so much I began the next and then halted, remembering the other reading I first needed to complete.

So, I finished the other book (Mythical Man Month
Rick Kober
When starting my first job out of college, part of the training was to read selected chapters from this book. The way that Steve McConnell presents the topics in story form made the reading effortless and even entertaining. Although I had initially suspected that the book reading was some useless filler task while they found something for me to do, looking back I probably learned more about programming on a team than I did during the first two years of college programming courses.

The book tackle
Excellent book on software development. I read the first version years ago. It was well worth picking up the second version as a refresher. The book covers everything from personal character to how to format a for loop, it's a must read for improving your skills and to help you realize how far you still have to go.

The only problem I have with the book is the formatting. It's a nightmare of little quotes, references and key point icons (with a picture of a key - thanks...) cluttering up each page
Well, it's definitely long. If you've been programming for a while, and haven't read this (like me), then you'll find it to be a good structured outline of what you're doing already, with quite a few new things sprinkled in.

For a recent grad, I think this book will be filled with lots of information that can help the new grad avoid the gotchas that had to be learned the hard way by other people.

I think Steve McConnell takes a fairly pragmatic approach in this book, in that he's for the most part
Toby Reiter
Aug 27, 2007 Toby Reiter rated it 5 of 5 stars  ·  review of another edition
Recommends it for: programmers/developers
This book is a really good examination of low-level design of code. This older version was written before widespread adoption of Java, web development, or object oriented development. However, it's focus on well-designed routines (methods/functions) meant that the meat of the content was still highly useful and actually unencumbered by more hyped up features of more recent programming trends.

The new version, Code Complete Second Edition includes content about newer programming techniques, includ
Alan Fay
I probably got less out of the book, having worked as a developer for a couple of years out of school, than say, a college student or somebody fresh out. Or maybe dinosaurs that are out of touch and need to get back into the game.

The second half of the book is pretty much a catalog of refactoring techniques. It's definitely geared towards the aforementioned audiences.

McConnell covers a few other topics, related to design, teamwork, testing, and configuration management, but doesn't go into dept
Aaron Boushley
Nov 28, 2011 Aaron Boushley rated it 3 of 5 stars
Recommends it for: beginning programmers
Shelves: programming
This book was a pretty good read. Most of what is discussed is extremely valuable information. Although with only 5 years of experience I felt like many of the points that Steve brought up were fairly obvious once you've been working as a Software Developer. If you are new to programming, want to move to a more professional level of programming or just plain have plenty of time on your hands this is a great book. However, if you already have a fair amount of experience developing software profes ...more
It is a nice book but too MS-centric. Some of the things are
going to confuse you if you come from a different environment. For example, it took me a while to realize that the term "magic number" was used for hard-coded constants; in Unix, the magic number is used to identify file type as described in /etc/magic. Similarly, the author did not like the indentation standard use by Gnu. There was something he did not like about Kernighan and Ritchie either Overall, I still think it was a decent boo
All the while reading this book, I struggled with how to rate it here. In many ways, this is an extraordinary piece of work; it's extremely comprehensive, and reveals a remarkable level of insight.

This second edition is from 2004, and although obviously some of its content may seem a little dated, most of it still holds up well in 2015. Given that context, I find it difficult to find fault with most of the book. Much of the advice given is good advice, and as a programmer, you should adopt and i
Rakesh Gopal
HIGHLY RECOMMENDED for any software programmer. McConnell writes clearly about why code should be written to be read and modified by others (and yourself). And not to be written just for the sake of being executed by a machine. He finely touches every aspect of how to:
1. Use Object Oriented Programming, the right way.
2. To modularize the code, optimal size of functions and classes, etc.
3. Got lot of code snippets that will be useful for day-to-day programming.
4. Unbiased both-side story, whereve
Not terrible, but not great, this book has a much higher stature among Microsofties than is strictly deserved, and little visibility beyond that group. Says nothing in 960 pages that The Practice of Programming doesn't manage to convey more clearly and succinctly in 267. Ok as a supplement to the latter for those looking for longer justifications for the same recommendations, or those deathly allergic to Unixisms. Pointless otherwise.
It's not bad book. It's good book, a lot of effort was spent to write it. But it's so... old school. Too bloated. Every idea is discussed according to some statistics and based on some computer science article. I don't like this "complete" approach very much. I prefer strong focus on topic and clear opinons based on real experience. If you like reading a dictionary, add another two stars.
Kevin Garner
"Code Complete" is a treatise on best practices for programming, centering primarily around the task of software construction. It provides advice relevant to programmers right now, even though the book's latest edition was published in 2004. The long shelf-life of this book is a tribute to its relevance as it emphasizes code readability and "coding for the maintenance programmer." The book also covers code tuning, testing, project scaling concerns, quality assurance, ideal programmer character t ...more
Andre T
Often regarded as the one book you must read if you care about programming well and I'm beginning to understand...

Only a five chapters in, I can see it's already improving not only my programming skills, but also with how to correctly deal with clients and bosses in order to minimize risk and increase productivity.

More thoughts on it will be posted later.

Nick Gotch
There's a lot of good stuff in here for new developers, which is why I gave it 3 not 2 stars. I thought some of it was a little dry and I'd already read of many of the practices the book mentions, which is why it didn't score higher with me. That said, it really is a good book for new developers.
Jim Crapia
Taking it for what it tries to do, this book is a must-read for anyone pursuing a career as a software engineer. While not perfect, McConnell builds not a reference but a mind set for responsible, sensible development, not just of software but of people who put it together.
Wilfredo Malazarte
Finally finished it after attempting it repeatedly over the past 8 years. Very good tips but EXTREMELY dense. If you want the TL;DR read the last 3 chapters. From there, you can then go through whichever chapters you want information on.
Alfredo Chavez
Some of McConnell points of view seem "completely wrong" when viewed from a post-agile era point of view. However, they reflect the sector where the majority of author's experience comes from: DoD contracting. You can hardly imagine a more demanding environment to make one's self a name.

Don't expect an Agile/Non-agile discussion here, even though the author has very specific ideas on the matter.

Do expect, however, very solid advice backed by hard data and tons of hands-on experience and academic
Christophe Keromen
Jun 10, 2010 Christophe Keromen rated it 5 of 5 stars
Recommends it for: every developer
The best book I read on the subject, ok I didn't read so many :-)
Many advises are advocated using statistics not only personal feeling
The author tries to take the best from each method avoiding religious commitment to one church
Nathan Glenn
McConnell uses personal experience along with hard data from many other researchers in industry and academia to show the reader how to write code quickly, efficiently, effectively, and bug-free.
Ronald Rajagukguk
This is the must read book for every programmer who want to start their very first career. Steve talks about how to write clean and readable code that will distinguish the good and bad programmer.
Andrew Dalgleish
This is probably in the top 5 of every good programmer's list of books that every programmer-to-be should read. I actually keep a copy of this in my bathroom.
« previous 1 3 4 5 6 7 8 9 99 100 next »
topics  posts  views  last activity   
URL for online copy of book 1 42 Oct 26, 2011 01:50PM  
  • Refactoring: Improving the Design of Existing Code
  • Programming Pearls
  • The Pragmatic Programmer: From Journeyman to Master
  • Design Patterns: Elements of Reusable Object-Oriented Software
  • The Practice of Programming
  • The Mythical Man-Month: Essays on Software Engineering
  • Clean Code: A Handbook of Agile Software Craftsmanship
  • Working Effectively with Legacy Code
  • Head First Design Patterns
  • Beautiful Code: Leading Programmers Explain How They Think
  • Domain-Driven Design: Tackling Complexity in the Heart of Software
  • Test Driven Development: By Example
  • Structure and Interpretation of Computer Programs (MIT Electrical Engineering and Computer Science)
  • Effective C++: 55 Specific Ways to Improve Your Programs and Designs
  • Refactoring to Patterns
  • Joel on Software
  • Compilers: Principles, Techniques, and Tools
  • Peopleware: Productive Projects and Teams

Goodreads is hiring!

If you like books and love to build cool products, we may be looking for you.
Learn more »
Rapid Development: Taming Wild Software Schedules Software Estimation: Demystifying the Black Art Software Project Survival Guide Professional Software Development: Shorter Schedules, Higher Quality Products, More Successful Projects, Enhanced Careers After the Gold Rush: Creating a True Profession of Software Engineering

Share This Book

No trivia or quizzes yet. Add some now »

“Programmers working with high-level languages achieve better productivity and quality than those working with lower-level languages. Languages such as C++, Java, Smalltalk, and Visual Basic have been credited with improving productivity, reliability, simplicity, and comprehensibility by factors of 5 to 15 over low-level languages such as assembly and C (Brooks 1987, Jones 1998, Boehm 2000). You save time when you don't need to have an awards ceremony every time a C statement does what it's supposed to.” 3 likes
“Heuristic is an algorithm in a clown suit. It’s less predictable, it’s more fun, and it comes without a 30-day, money-back guarantee.” 2 likes
More quotes…