I'll second that. Under Pressure was a very good book.
Code Complete should be required reading for every single programmer, regardless of how long they've been at it.
I've been programming for 20+ years and still found CC to be a great book. A lot of good tips/suggestions/reasoning in there, and very good explanation as to why those recommendations are what they are.
It doesn't need to be followed to the letter, but there are some major Best Practices in there, allowing you to choose and follows the ones best suited for you and your organization.
I read the original and actually would like to go back and read CC2 now, just to 1) Get some more info and 2) see what new changes are in it.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.