Archived

This topic is now archived and is closed to further replies.

Flint

Code Complete

Recommended Posts

Good book to help you become an all-around better programmer. Covers how to organize your code, comment better, use variables better (naming and scope, etc). Non-language specific. Recommended reading.

Amazon.com:
Believed by many of our customers to be the best practical guide to writing commercial software, and Highly Recommended.

From Book News, Inc:
The concepts discussed in this encyclopedic treatment are applicable to any procedural language in any computing environment. The presentation, intended to help developers take strategic action rather than fight the same battles again and again, includes some 500 examples of code (good and bad), along with checklists for assessment of architecture, design approach, and module and routine quality.

Share this post


Link to post
Share on other sites
Heh, by chance I just read one of your post in the beginners forums before coming here. You''re teaching yourself how to programming using Accelerated C++, right? or are you learning C++ and already know how to program?

Code Complete is a practical book on writing software. In contains little (if any) theory, instead focusing on what you should do and why. To this end it does not cover any one subect in great detail, gut gives you some working knowledge in a number of areas. It might be a little premature for you to start reading Code Complete now, but it is worth reading in the near future. The author doesn''t ever seem to specifically "vocalize" it, but the book is (primarily) about intristic software qualities - this means it''s about a subset of software architecture.

If you already know some other languages and/or have already written some programs, then Code Complete is good book to read.

Share this post


Link to post
Share on other sites
Code Complete is a great book to read once you are fairly familiar with programming. One criticism of it is that it sometimes focuses on code features and paradigms that are quite outdated, but in fact the thinking behind the points is still as valid today as it was then. The only difference is that the examples may not seem as immediately relevant. But everyone should read it at least once.

[ MSVC Fixes | STL | SDL | Game AI | Sockets | C++ Faq Lite | Boost | Asking Questions | Organising code files | My stuff ]

Share this post


Link to post
Share on other sites