Code Complete Quotes

Rate this book
Clear rating
Code Complete: A Practical Handbook of Software Construction Code Complete: A Practical Handbook of Software Construction by Steve McConnell
9,456 ratings, 4.30 average rating, 446 reviews
Open Preview
Code Complete Quotes Showing 121-150 of 130
“Immature testing organizations tend to have about five clean tests for every dirty test.”
Steve McConnell, Code Complete
“developer testing should probably take 8 to 25 percent of the total project time.”
Steve McConnell, Code Complete
“code reading detected about 80 percent more faults per hour than testing”
Steve McConnell, Code Complete
“it's better to strive for a good solution and avoid disaster rather than trying to find the best solution”
Steve McConnell, Code Complete
“Be sure that the names you choose favor read-time convenience over write-time convenience.”
Steve McConnell, Code Complete
“in the vast majority of systems, efficiency isn't critical.”
Steve McConnell, Code Complete
“Favor read-time convenience to write-time convenience. Code”
Steve McConnell, Code Complete
“When in doubt, use brute force.”
Steve McConnell, Code Complete
“An algorithm gives you the instructions directly. A heuristic tells you how to discover the instructions for yourself, or at least where to look for them.”
Steve McConnell, Code Complete
“In software, consultants sometimes tell you to buy into certain software-development methods to the exclusion of other methods. That’s unfortunate because if you buy into any single methodology 100 percent, you’ll see the whole world in terms of that methodology. In some instances, you’ll miss opportunities to use other methods better suited to your current problem.”
Steve McConnell, Code Complete

1 2 3 5 next »