Steve McConnell
Steve McConnell
Steven C. McConnell is an author of software engineering textbooks such as Code Complete, Rapid Development, and Software Estimation. He is cited as an expert in software engineering and project management...
NationalityAmerican
ProfessionAuthor
CountryUnited States of America
Steve McConnell quotes about
teamwork strong together
In software, the chain isn't as strong as its weakest link; it's as weak as all the weak links multiplied together.
teamwork jobs average
The job of the average manager requires a shift in focus every few minutes. The job of the average software developer requires that the developer not shift focus more often than every few hours.
engineering principles ends
Engineering is the application of scientific principles toward practical ends. If the engineering isn't practical, it's bad engineering.
mistake blanket biggest-mistake
A blanket attempt to avoid mistakes is the biggest mistake of all.
teamwork hard-work people
Even when you have skilled, motivated, hard-working people, the wrong team structure can undercut their efforts instead of catapulting them to success. A poor team structure can increase development time, reduce quality, damage morale, increase turnover, and ultimately lead to project cancellation.
design force brutes
A brute force solution that works is better than an elegant solution that doesn't work.
dirty long forgotten
The trouble with quick and dirty is that dirty remains long after quick has been forgotten.
funny-inspirational errors coders
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 error-free.
code-quality logical program
Good visual layout shows the logical structure of a program.
teamwork two failing
Software projects fail for one of two general reasons: the project team lacks the knowledge to conduct a software project successfully, or the project team lacks the resolve to conduct a project effectively.
technology documentation programming
Good code is its own best documentation.
waiting firsts software
It's better to wait for a productive programmer to become available than it is to wait for the first available programmer to become productive.
air upset three
... programming requires more concentration than other activities. It's the reason programmers get upset about 'quick interruptions' - such interruptions are tantamount to asking a juggler to keep three balls in the air and hold your groceries at the same time.
code-quality errors simplicity
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 weight by weighing yourself more often. What you eat before you step onto the scale determines how much you will weigh, and the software development techniques you use determine how many errors testing will find. If you want to lose weight, don't buy a new scale; change your diet. If you want to improve your software, don't test more; develop better.