На удивление простая в понимании (несмотря на объём) книга. Развернуто и по делу. Хвалить можно долго, и разумеется заслуженно. Не зря ее включают во все списки книг для разработчиков ПО.

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, with section headlines aligned on the quotes rather than the sections and further reading material listed every few pages rather than at the end. Given the focus the book has on readable code it's a shame the book format is such a dog's breakfast.

I feel like I should have read it earlier in my carrier. It is a good book. But it felt boring to me because I already knew most of the stuff. Did not live up to my expectations because people say it is the Bible of programming. However, I would say that Clean Code by Uncle Bob is more interesting and more useful for me at this point.

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 tackles more than just the technical look at coding, but delves into the deeper thought processes involved in writing software. I would strongly recommend this book to anyone interested in working with software of any kind. In fact, in the time since starting my job I have helped train two new members to my software team, and reading Code Complete was the first things I had them do.

A lot of interesting stuff in it but also a lot of stuff that is simply not as important as it was in the past. It's not a cover to cover book to me but I will have a look at it again once I need to dig deep into a specific topic.

I'm keeping this book on my bookshelf. It's a good read and great for developers. I realised as I was reading that I had already learned a lot of the concepts and principles throughout my time in school for a computer science degree and also my internships with Microsoft. But it's important to refresh and consume the topics in a way that helps me put into words what "intuitions" I've built. There were also a lot of bad habits that I have as a programmer that reading this book has helped me to notice and I think in a year or a few I'll read it again to see if I've changed those bad habits.

That book was for me high expectation.
But in real case, for 10 years of professional development and self improvement, that book is just repeating of basic paradigms. But still I found something new. May be not new, but obvious, what most of senior developers ignores by "authority" of experience.



I recommend that book for Mid-Senior developers. It collects a ton of best practices and advices.
For junior devs it will be hard to handle at once. Needs to return back more that once.
At least, once you must read. Later you could return to it, to refresh knowledge about that obvious stuff, what we start to ignore with time.

For me is main idea of that book.
1. Struggle with code complexity
2. Be curious
3. Programming is intellectual work - you must remember it. Work with you head!

It's a great book for fresher developers, as it contains a lot of practices and hard facts to back them up. I''m already aware of quite of bit that the book advocates so I wouldn't get as much out of it as a new developer. But having said that, I did get to learn bits and pieces here and there of stuff I hadn't thought about, so it's good. I guess the downside about this book is that it can be pretty long-winded in trying to explain why a certain practice is a good practice.

Often called "'The Joy of Cooking' for coding", Code Complete is an excellent book that doesn't say HOW TO code, but is ABOUT coding. Considerations with project size and complexity, coding style, comments, testing strategies, even developer communication are all touched upon.

Many things won't click with people who don't have at least a year or two of development under their belt, but for any kind of programmer, this book contains many gems that are worth referencing for years to come.

Detailed explanation with good examples, thoughtful quotes just in-place, pointers to relevant literature, actionable check-lists and key points. It's one of the must-reads.

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 strictly covering processes/conventions that any developer at any size shop should be following.

I think this is a must read for any professional programmer.

This is a solid overview of the practice of software design at a low level: not how to solve problems with logical architecture, but how to organize code (or what the author calls "construction"). As of time of reading, I've been programming for fifteen years. For me, much of this was tread ground but I think reading this book would be as good as a year or two of practical experience, at the least, for a beginning programmer. It would certainly set them off on the right foot. If I'd read it a decade or so ago it would have saved me a lot of unnecessarily painful learning experiences and teachable moments.

Even as an experienced programmer, I still picked up a few concepts from this book. Beyond that I picked up a lot of useful metaphors and documented research which I plan to employ in the future when explaining concepts to other professionals.

Code Complete is a bit dry, but it's also well-organized so the reader can easily skip to the sections most relevant to their interests. There's also a fantastic extended reading list at the end which I'm now planning to dive into.