Quality Software Quotes & Sayings

Developer testing is an important step towards accountability. It gives developers a way to demonstrate the quality of the software they produce. — Kent Beck

High-quality software is not expensive. High-quality software is faster and cheaper to build and maintain than low-quality software, from initial development all the way through total cost of ownership. — Capers Jones

Poor-quality software has all the subtlety of a neighborhood ice cream truck. You know it's bad for you; you know it's coming a mile away; yet you can't resist. — Eric Brechner

While it is becoming increasingly obvious that the fundamental architecture of a system has a profound Influence on the quality of its human factors, the vast majority of human factors studies concern the surface of hardware (keyboards, screens) or the very surface of the software (command names, menu formats). — Lewis M. Branscomb

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. — Steve McConnell

Software never was perfect and won't get perfect. But is that a license to create garbage? The missing ingredient is our reluctance to quantify quality. — Boris Beizer

At first I hoped that such a technically unsound project would collapse but I soon realized it was doomed to success. Almost anything in software can be implemented, sold, and even used given enough determination. There is nothing a mere scientist can say that will stand against the flood of a hundred million dollars. But there is one quality that cannot be purchased in this way - and that is reliability. The price of reliability is the pursuit of the utmost simplicity. It is a price which the very rich find most hard to pay. — C.A.R. Hoare

Improve performance through process improvements introduced with minimal resistance. Deliver with high quality. Deliver a predictable lead time by controlling the quantity of work-in-progress. Give team members a better life through an improved work/life balance. Provide slack in the system by balancing demand against throughput. Provide a simple prioritization mechanism that delays commitment and keeps options open. Provide a transparent scheme for seeing improvement opportunities, thereby enabling change to a more collaborative culture that encourages continuous improvement. Strive for a process that enables predictable results, business agility, good governance, and the development of what the Software Engineering Institute calls a high-maturity organization. — David J. Anderson

Yet, I am convinced that there is a need for high quality software, and the time will come when it will be recognized that it is worth investing effort in its development and in using a careful, structured approach based on safe, structured languages. — Niklaus Wirth

You can either have software quality or you can have pointer arithmetic, but you cannot have both at the same time. — Bertrand Meyer

The goal of Continuous Delivery is to create a constant flow of changes to production: an automated software production line. The core concept that makes this happen is the Continuous Delivery pipeline. The pipeline breaks the software delivery process down into a number of stages. Each stage is aimed at verifying quality of new features from a different angle in order to prevent errors from affecting your users. — Andrew Phillips

The Core Debugging Process
The core of the debugging process consists of four steps:
Reproduce:
Find a way to reliably and conveniently reproduce the problem on demand.

Report erratum Prepared exclusively for castLabs GmbH this copy is (P2.0 printing, February 2010)
FIRST THINGS FIRST 18
Diagnose:
Construct hypotheses, and test them by performing experiments until you are confident that you have identified the underlying cause of the bug.
Fix:
Design and implement changes that fix the problem, avoid intro- ducing regressions, and maintain or improve the overall quality of the software.
Reflect:
Learn the lessons of the bug. Where did things go wrong? Are there any other examples of the same problem that will also need fixing? What can you do to ensure that the same problem doesn't happen again? — Paul Butcher

Some software is actually pretty good, by any standard. Think of the Mars Rovers, Google, and the Human Genome Project. Now, that's quality software! — Bjarne Stroustrup

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. — Steve McConnell

The Apple Marketing Philosophy" that stressed three points. The first was empathy, an intimate connection with the feelings of the customer: "We will truly understand their needs better than any other company." The second was focus: "In order to do a good job of those things that we decide to do, we must eliminate all of the unimportant opportunities." The third and equally important principle, awkwardly named, was impute. It emphasized that people form an opinion about a company or product based on the signals that it conveys. "People DO judge a book by its cover," he wrote. "We may have the best product, the highest quality, the most useful software etc.; if we present them in a slipshod manner, they will be perceived as slipshod; if we present them in a creative, professional manner, we will impute the desired qualities. — Walter Isaacson

Today I am more convinced than ever. Conceptual integrity is central to product quality. Having a system architect is the most important single step toward conceptual integrity. These principles are by no means limited to software systems, but to the design of any complex construct, whether a computer, an airplane, a Strategic Defense Initiative, a Global Positioning System. After teaching a software engineering laboratory more than 20 times, I came to insist that student teams as small as four people choose a manager and a separate architect. Defining distinct roles in such small teams may be a little extreme, but I have observed it to work well and to contribute to design success even for small teams. — Frederick P. Brooks Jr.

I write them to improve my productivity as a programmer. Making the quality assurance department happy is just a side effect. Unit tests are highly localized. Each test class works within a single package. It tests the interfaces to other packages, but beyond that it assumes the rest just works.

Functional tests are a different animal. They are written to ensure the software as a whole works. They provide quality assurance to the customer and don't care about programmer productivity. They should be developed by a different team, one who delights in finding bugs. — Martin Fowler

Quality Never dies. — Abdullah Khan

Releasing Linux versions has always been a matter of higher code quality, good software architecture, and technical interest for the platform. — Timothee Besset

To treat programming scientifically, it must be possible to specify the required properties of programs precisely. Formality is certainly not an end in itself. The importance of formal specifications must ultimately rest in their utility -in whether or not they are used to improve the quality of software or to reduce the cost of producing and maintaining software. — Jim Horning

Talking about Apple v. Microsoft without mentioning the Internet and the browser is like talking about WWII without talking about the nuke. Framing the conversation just in terms of open v. closed operating systems, the quality of the hardware or software or who the CEO was, is silly. — Michael Arrington

We know about as much about software quality problems as they knew about the Black Plague in the 1600s. We've seen the victims' agonies and helped burn the corpses. We don't know what causes it; we don't really know if there is only one disease. We just suffer - and keep pouring our sewage into our water supply. — Tom Van Vleck

If you think your management doesn't know what it's doing or that your organisation turns out low-quality software crap that embarrasses you, then leave. — Edward Yourdon