Code Complete: A Practical Handbook of Software Construction, Second Edition - page 1
- Code Complete, Second Edition
- Code Complete, Second Edition
- Table of Contents
- Copyright
- Preface
- Who Should Read This Book?
- Where Else Can You Find This Information?
- Key Benefits of This Handbook
- Why This Handbook Was Written
- Author Note
- Acknowledgments
- About the Author
- Steve McConnell
- Part I: Laying the Foundation
- In this part:
- Chapter 1. Welcome to Software Construction
- 1.1. What Is Software Construction?
- 1.2. Why Is Software Construction Important?
- 1.3. How to Read This Book
- Key Points
- Chapter 2. Metaphors for a Richer Understanding of Software Development
- 2.1. The Importance of Metaphors
- 2.2. How to Use Software Metaphors
- 2.3. Common Software Metaphors
- Key Points
- Chapter 3. Measure Twice, Cut Once: Upstream Prerequisites
- 3.1. Importance of Prerequisites
- 3.2. Determine the Kind of Software You re Working On
- 3.3. Problem-Definition Prerequisite
- 3.4. Requirements Prerequisite
- 3.5. Architecture Prerequisite
- 3.6. Amount of Time to Spend on Upstream Prerequisites
- Additional Resources
- Key Points
- Chapter 4. Key Construction Decisions
- 4.1. Choice of Programming Language
- 4.2. Programming Conventions
- 4.3. Your Location on the Technology Wave
- 4.4. Selection of Major Construction Practices
- Key Points
- Part II: Creating High-Quality Code
- In this part:
- Chapter 5. Design in Construction
- 5.1. Design Challenges
- 5.2. Key Design Concepts
- 5.3. Design Building Blocks: Heuristics
- 5.4. Design Practices
- 5.5. Comments on Popular Methodologies
- Additional Resources
- Key Points
- Chapter 6. Working Classes
- 6.1. Class Foundations: Abstract Data Types (ADTs)
- 6.2. Good Class Interfaces
- 6.3. Design and Implementation Issues
- 6.4. Reasons to Create a Class
- 6.5. Language-Specific Issues
- 6.6. Beyond Classes: Packages
- Additional Resources
- Key Points
- Chapter 7. High-Quality Routines
- 7.1. Valid Reasons to Create a Routine
- 7.2. Design at the Routine Level
- 7.3. Good Routine Names
- 7.4. How Long Can a Routine Be?
- 7.5. How to Use Routine Parameters
- 7.6. Special Considerations in the Use of Functions
- 7.7. Macro Routines and Inline Routines
- Key Points
- Chapter 8. Defensive Programming
- 8.1. Protecting Your Program from Invalid Inputs
- 8.2. Assertions
- 8.3. Error-Handling Techniques
- 8.4. Exceptions
- 8.5. Barricade Your Program to Contain the Damage Caused by Errors
- 8.6. Debugging Aids
- 8.7. Determining How Much Defensive Programming to Leave in Production Code
- 8.8. Being Defensive About Defensive Programming
- Additional Resources
- Key Points
- Chapter 9. The Pseudocode Programming Process
