One of the huge initial proponents of quality was a man named 'Philip Crosby', You can find a quick overview here. One of the toughest tasks in production is quality and defining it. Here is a excellent overview of quality management.
Four Absolutes of Quality Management
As far as IT goes, trying to write code to requirements can be tough. You are often working with people who do not understand what type of product they want or how to write requirements. On the other hand, you will have programmers that don't understand enough about the business to fill in the gaps that the rest of the business may know.
Another area that a number people miss No 2, prevention leads to quality not appraisal. What I mean by this is error handling when it comes to getting your data from somewhere else. A good example is when programmers don't use place holders when doing a SQL query, but instead just stick raw values from the client. The result was a number of applications that are vulnerable to SQL injection attacks.
You are correct, Quality is the toughest one, but it is not a developer issue, but a management issue as well. Quality often requires to sit down and do some real work, and to be honest most people are reluctant to do that, especially when they think they can pass that work off onto the programmer because "Their smart, they will figure it out."
In reply to Re: The dangers of perfection, and why you should stick with good enough
by Herkum
in thread The dangers of perfection, and why you should stick with good enough
by redhotpenguin
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |