I personal believe problems and quality are pretty clear. The challenge is in understanding what the problem is, which is not a "programming" activity, but ra

I personal believe problems and quality are pretty clear. The challenge is in understanding what the problem is, which is not a "programming" activity, but rather a communication activity. You could have 2 customers who want a solution that clash and conflict, if you make one happy, you make the other sad. No matter how you tackle it, you lose. e.g. You build something for sales that makes customer service unhappy or vice versa. You build something and keep it backwards compatible and that makes your prior users happy but puts off new users who were willing to adopt or vice versa. At this point, it's no longer about programming. Doesn't diminish that those activities are just important. We could also argue that there are 10x user interface and interaction designers, 10x project managers, 10x product managers, etc. The confluence of such folks is a beautiful thing to experience, however it's not needed, just 1 or 2 of those with a bunch of "average" folks can ship and release a really good product.