The default movement on a software project should be in the direction of taking elements of the software away to make it simpler rather than adding elements to make it more complex. — Steve McConnell Copy Share Image
Testing by itself does not improve software quality. Test results are an indicator of quality, but in and of themselves, they don't improve it. Trying to improve software quality by increasing the amount of testing is like trying to lose… — Steve McConnell Copy Share Image
... programming requires more concentration than other activities. It's the reason programmers get upset about 'quick interruptions' - such interruptions are tantamount to asking… — Steve McConnell Copy Share Image
The job of the average manager requires a shift in focus every few minutes. The job of the average software developer requires that the… — Steve McConnell Copy Share Image
“usually more time is spent in making good-looking presentation slides than in improving the quality of the software.” — Steve McConnell Copy Share Image
It's hard enough to find an error in your code when you're looking for it; it's even harder when you've assumed your code is… — Steve McConnell Copy Share Image
“the error rate in manual testing is comparable to the bug rate in the code being tested.” — Steve McConnell Copy Share Image
“[...] you shouldn't be uneasy about any parts of the architecture. It shouldn't contain anything just to please the boss. It shouldn't contain anything… — Steve McConnell Copy Share Image
It's OK to figure out murder mysteries, but you shouldn't need to figure out code. You should be able to read it. — Steve McConnell Copy Share Image
“Programmers working with high-level languages achieve better productivity and quality than those working with lower-level languages. Languages such as C++, Java, Smalltalk, and Visual… — Steve McConnell Copy Share Image
The trouble with quick and dirty is that dirty remains long after quick has been forgotten. — Steve McConnell Copy Share Image