✳flâneur — a map of the web's best reading

Notes on software quality

anthonyhobday.com · 5,748 words · saved by 2 readers

The most practical way to measure quality is to test with many different people, and have many experts take a look. If thorough testing and 100 experts can’t find a problem, the thing is probably perfect. Perfection is impossible. The agreed-upon best-designed software in the industry has noticeable problems. But the closer you can get, the better. The closer you try to get to perfection, the harder it is. This is the same “diminishing returns” effect you’ll see anywhere quality is involved. Leadership and culture both define and allow quality. Even if they don’t believe they do. Even if they haven’t thought about it. Their actions and beliefs will either enable or limit quality. Quality is a result of ability and appetite. Does the organisation have people who can produce high quality (ability)? And does the organisation allow quality to be achieved (appetite)? ~100% of the time I’ve seen an organisation make high quality software, it is because the leaders wanted it. If the leaders d

Notes on software quality Jump to: How I think about quality Universal signals of quality The six signals of quality in software The benefits of software quality Beliefs about quality I want to disprove Quality is impossible at scale Anecdotal evidence that quality is impossible at scale Companies with dedicated quality efforts Interface quality of life improvements How I think about quality Quality is the absence of problems “The absence of problems” is the best definition I can come up with for quality. The most practical way to measure quality is to test with many different people, and have

Explore this link on the map →

saved by

related reading