"... We've failed not because nobody wanted our product. Or because of missing programming skills. We've failed because we've lost faith in our product! ..." F

"... We've failed not because nobody wanted our product. Or because of missing programming skills. We've failed because we've lost faith in our product! ..." Faith in product or self? I think you are right to question the ratio of HN articles readers obsess over at the expense of psychology. You want to build something, but first you have to overcome many hurdles. Somewhere along on the way the balance of motivation and flexibility that keeps hackers working on projects gets out of whack, code stops getting written and your project dies. Overcoming obstacles is what it's all about. If you avoid signs of failure [0] you have a better chance of completing the project. This of course doesn't mean the project is worthy of being called a product. Users just might not like what you have to offer. Not completing the project/product is the quickest way to failure. There are no easy answers here. Keep moving forward. [0] Reading this motivates me to finish an article I've been planning on failure. Here's some patterns of failure I've noticed ~ http://seldomlogical.com/2009/08/12/10-signs-of-failure http://seldomlogical.com/2009/08/12/10-signs-of-failure