Code Complete (Microsoft Programming) [ペーパーバック]

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

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.

I thought it's just the experience and knowledge of almost all the possible (MFC) functions that exist. Code Complete showed me that it's a lot more than that, beginning by designing your program, not just starting to write code right away, up to topics like naming conventions for variables, how to determine what code to put into a routine or how to make your program easier to debug.

Although Code Complete may sound like a very dry book only for expert programmers, it really isn't. Steve McConnell even managed to throw in a lot of amusing anecdotes or witty tests - like the one: "How many of these data structures do you know?". If you checked (almost) ALL of them, you're advised to read the section about intellectual honesty - because some of the data structures are bogus names made up by the author. :)

All in all, I HIGHLY recommend this book to anyone , whether you're a professional programmer (for me that is any programmer whose job is programming <g>) or a hobbyist like me, wanting to create the applications you always dreamed of but thought you could never manage it.

Especially interesting for students or anyone trying to start a career as a programmer: this book contains a lot of 'further reading' advices with short descriptions of the books. So this book is also an excellent entry point for those wanting to become a professional programmer and are looking to fill the mind gaps where necessary.