Home / Authors / Steve McConnell

Steve McConnell

Steve McConnell Quotes

Author

Steve McConnell is a renowned software engineering author. His works, 'Code Complete' and 'Software Craftsmanship', have had a profound impact on the software industry. McConnell has extensive experience in software engineering and has held key roles in multiple large projects.

Famous Steve McConnell Quotes

“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.”

Hard Enough Harder Errors Code Programming Software Funny Inspirational Computer Programming Software Engineering Computer Software Coders

Author:Steve McConnell

“Good code is its own best documentation. As you're about to add a comment, ask yourself, "How can I improve the code so that this comment isn't needed?" Improve the code and then document it to make it even clearer.”

Asks Needed Add Code Programming Comment Documents Funny Inspirational Computer Programming Programming Languages Computer Language Software Engineering Documentation

Author:Steve McConnell

“Good code is its own best documentation.”

Technology Computer Code Programming Computer Programming Computer Science Programming Languages Computer Language Documentation

Book:Code Complete

Source: Code Complete

“It's OK to figure out murder mysteries, but you shouldn't need to figure out code. You should be able to read it.”

Needs Should Able Mystery Figures Computer Murder Code Programming Software Programmers Computer Programming Programming Languages Computer Language Software Engineering Computer Programmers Computer Software Murder Mysteries

Book:Code Complete

Source: Code Complete

“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.”

Firsts Waiting Computer Available Programming Productive Software Programmers Software Engineering

Book:Software Project Survival Guide

Source: Software Project Survival Guide

“... 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.”

Reason Three Air Activity Balls Asking Upset Programming Concentration Software Groceries Programmers Interruptions Software Engineering Jugglers

Author:Steve McConnell

“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.”

Source: Code Complete

“A brute force solution that works is better than an elegant solution that doesn't work.”

Force Design Solutions Programming Elegant Brutes Software Engineering Brute Force Elegant Solutions

Book:Code Complete

Source: Code Complete

“Good visual layout shows the logical structure of a program.”

Shows Quality Program Structure Code Visuals Programming Logical Software Engineering Layout Code Quality

Author:Steve McConnell

“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.”

Jobs Hours Focus Minutes Average Managers Programming Teamwork Software Developers Software Engineering Staffing

Book:Software Project Survival Guide

Source: Software Project Survival Guide

“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.”

Source: Rapid Development

“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.”

Two Reason Failing Team Projects Programming Resolve Teamwork Software Software Engineering Staffing

Book:Software Project Survival Guide

Source: Software Project Survival Guide

“In software, the chain isn't as strong as its weakest link; it's as weak as all the weak links multiplied together.”

Together Strong Weak Chains Programming Links Teamwork Software Software Engineering Staffing Weakest Link

Book:Code Complete

Source: Code Complete

About the Author

Born: September 3, 1962
Known for: Author
Quotes: 28

Popular Topics

People Ifs Thinking Knows Men World Way Want Love Life Inspirational Needs Giving Feels Should Writing Trying Years Mind Firsts

Books & Sources

Code CompleteRelated source material

Software Project Survival GuideRelated source material

Rapid DevelopmentRelated source material

After the Gold Rush: Creating a True Profession of Software EngineeringRelated source material

Code Complete: A Practical Handbook of Software ConstructionRelated source material

Software Estimation: Demystifying the Black ArtRelated source material

Similar Authors

Niklaus WirthBrowse related quotes
Martin FowlerBrowse related quotes
Fred BrooksBrowse related quotes
Larry ConstantineBrowse related quotes
Barry BoehmBrowse related quotes
Tony HoareBrowse related quotes
David ParnasBrowse related quotes
Brian KernighanBrowse related quotes
Edsger DijkstraBrowse related quotes
Friedrich L. BauerBrowse related quotes