"Build something people need and love. People will talk about it."
People can only talk about it if they know about it. How will they know?
"Release, release and release. Release it before you think it's ready, you're wrong, you don't need that feature."
This would be better said as, "If you're not quite sure, don't be afraid to release. Blindly releasing for the sake of releasing is risky and stupid."
"Your app will probably fail, most of them do."
What is this doing on this list? Worst advice ever. Better would be, "Your app can succeed."
"Build something you want to use. Continue to use it, feel the user's pain."
This can easily be the opposite of #1, "Build something people need and love." You're unnecessarily restricting yourself to the relatively tiny population of things that interest you.
"Be Ballsy, don't follow the herd, make a courageous moves."
Such as...
"Build something you want to use. Continue to use it, feel the user's pain."
Bad advice. Better to ask the user about their own pain. Developers are notorious for having blind spots about their own apps.
"Google Adwords isn't a revenue model."
Not according to Markus Frind, founder of plentyoffish.com.
"Find the cheapest, fastest way to 500 paid users. People will pay for your app, if it's good."
Such as...
"Design is an iterative process, not just development. And you won't get it right the first time, so don't sweat so much."
Sweat a little. Release shit too soon and shoot yourself in the foot. Development must be done with design in mind.
"Don't scale until you actually need to. (The front page of Digg does not count as need.)"
But develop with scaling in mind. (Will you really have enough time to completely redesign your data base schema after 1000 users?)
"Don't spend any money."
What if spending money is more time/cost effective? (Paying someone to do something that would have taken me 5 days to do.)