: Have peers review your low-level designs and code to catch errors early. 5. Personal Character and Craftsmanship
: Assume that users will provide bad data and that code will fail; write routines that protect themselves from invalid inputs. 3. Effective System Design Code Complete: A Practical Handbook of Software...
: Keep the "live time" of variables (the time between declaration and use) as short as possible to minimize mental load. : Have peers review your low-level designs and
McConnell emphasizes that being a great programmer is as much about character as it is about technical skill. Code Complete: A Practical Handbook of Software...