Well, you and I can disagree on the usefulness of this article then. By that analogy, I see quite a few concrete and "useful" details on how not to crash the plane, here.
It's just a nice summary of some common errors, with suggestions on how to avoid them. It's not the end-all utility to stop them from happening, but it's a good high level view.
Without even a single reference to "get to know your users"? Sorry, but no. It's not a nice summary; it's actually what I wouldn't give to students or someone wanting to get a grasp on UX.
This kind of "guidelines-based" approach is detrimental to UX, as it enforces the idea of focusing on details instead of considering UX as a whole.
It's just a nice summary of some common errors, with suggestions on how to avoid them. It's not the end-all utility to stop them from happening, but it's a good high level view.