(UTC) 

 The message may be dry but I think it touches the basic truth.  Minky's message probably misses the main point of the message.  I'm not talking about the importance of requirement or coding.  I'm defining what is quality with respect to software product.  Quality cannot be achieved by a single factor or a single element.  It is the accumulated results of many factors. 

 Most discussion focus in areas people working with.  However, it seldom try to view the quality from the user perspective.  User is the ultimate judge on the quality of product.  How often does a technically brilliant product fails to please users?  Usually, developer complaint that users can't understand the beauty of the product.  I'm no exception and I did that in the past.  However, I start to realize the cause is most likely the product fails to meet users' expectation.  Therefore, the technically brilliant product becomes a technically brilliant rubbish to the users. 

 This sounds very harsh.  But, I truly believe in this. 

   09:38, 2 April 2010