Rating:  Summary: Required Reading Review: I won't go into a review of the book as it has already been done so well by others here. Let me just say this:As you read through the reviews, note those that give this book less than 5 stars (save one poor misguided fellow who must think 1 star is better than 5). These are people that I end up sending 'sorry you didn't get the job' letters to whenever I hire new programming staff. The material in this book is so fundamental, so common sense, that it's easy to take it for granted. Don't. Buy a copy, and if you manage software projects and programmers buy copies for everyone involved (most of my people have copies of their own at home, I want them to have it available at work too). Then give them time to read it (or reread it). This will be the best investment in your staff you will ever make. During interviews the mention of this book by a candidate when I ask about their personal professional reading counts as highly as any single other factor (and slightly ahead of most 'professional certifications' since I've found these to be a better indicator of ones ability to take tests than to perform in a production environment). And don't forget to take your's down now and then as well.
Rating:  Summary: The best book I've ever read Review: About previous comments: Verbose? Don't think so, every page has some piece of valuable information For beginners only? Don't think so, but if you are a beginner this is a good place to start. After several years of programming you'll mostly stop thinking about style and follow your habits... so you better have some good habits! Insistence on using hungarian naming convention? Not at all, did you read this book? The author did talk about this convention but he also gives examples why this is can be bad (and also why it can be good). This book covers a wide range of material, from variable declaration to software estimation and probably everything concerning software construction. Also as this book talks a lot about style, the best thing is it is backed up with hard facts not just because of personal preference. The examples are written in several languages (such as C, Pascal and Basic). One chapter is devoted to object orientation. Although you're heavily into OOP then in no way should you skip over this book as the advices in this book can be applied to every methodology of programming. So this book is in no way out dated. Each chapter has a 'recommended reading' section so you know where to go for more. This is extremely handy. I've read this book several times and I just love it. I own every book written by the author. Check them out also - they are very good too. Summary: This book teaches you how you can write good and self-describing code. I wished every program I've had to read had been written by programmers who read this book and applied that knowledge. Thanks, ABO
Rating:  Summary: Over-hyped, disorganized laundry list Review: For the experienced programmer, "Code Complete" offers nothing useful. I bought this book with high expectations but found it to be a verbose enumeration of rudimentary software engineering and programming principles not worth the paper it was printed on. The application of common sense to coding is not revolutionary. Therefore, "Code Complete" is not worth your time because this is all it advocates, while taking over seven hundred pages to do it. The hype surrounding this book is, to my mind, thoroughly unexplainable. CAVEAT EMPTOR!
Rating:  Summary: Great book for beginners only Review: Junior programmers will probably enjoy this book, but profi programmers won't find more than 5% of this book useful. There is too much theory, and the whole book would fit to 300 pages (instead of 840). Buy this book if you dont have more than 2-3 years of software-construction experience. This book would deserve 5 stars, when you change the name to: "Code complete: a practical handbook of software construction for BEGINNERS". For experienced programmers is 3 stars rating of this book more than enough...
Rating:  Summary: Required reading Review: Q&A. Q: Do you want to be a *real* programmer ? A: Buy Code Complete
Rating:  Summary: Fundamentals people with advanced CS degrees didn't learn Review: Highest recommendation. A good treatment of the fundamental skills needed for writing readable, well structured code. I've seen so much code written in the latest languages, tools, and "paradigms" that's still buggy, low quality garbage because the programmers didn't master the fundamentals like how to write a decent procedure, or use meaningful variable names, or write useful comments. I wish I could give a copy of this book to the programmers whose code I maintain and get a court order to make them read every page before they touch a computer again.
Rating:  Summary: A must read... Review: This book should be considered mandatory reading for all I.T. project managers and CIO's. It puts software development into the right perspective.
Rating:  Summary: The Stadard Review: This IS the standard for professional code. Professionals use it, students use it. Anyone who doesn't is only asking for trouble. The principles in this book can be applied to any type of programming...stand-alone applications or CGI applications. It's how we rate ourselves as programmers.
Rating:  Summary: The best, of the very best computer book i've ever read Review: A must have, for every programmer that wants to do a better job
Rating:  Summary: great overall resource... with hops to expanding literature Review: I am a junior programmer that has been forces more or less into software engineering as well. Thanks McConnell state 6 seas are now only state 4. :) I am really impressed with this piece. It is a complete overview of the software developement philosophy with the emphasis on creating quality code. Where further information is Important McConnell has added copious qualifing titles and authors that will allow the reader to continue further investigation.
|