Most of those would be good pieces of advice given the right amount of context, but they are blown up into universal advice and, even worse, a "how to" (yes, I know the title of the original article doesn't say "How to", but it was posted to HN by its author, jason, and so he chose both titles!). This is not a "how to" for disruption. A better how-to for that topic would be this one: http://swombat.com/2011/2/18/how-to-develop-disruptive-ideas by someone who's written a book about the topic after spending much time studying it, and so has had the chance to develop a generic method.
Instead, this article is a collection of potentially good pieces of advice that can be deadly if used without being properly understood.
Anyway, so my point is, I think you can do much better than this, Jason, given your skill at writing and your breadth of knowledge of startups.