It seems a bit of a lazy article to me. So apologies but my reply is only brief and I am not going to spend a lot of time on it... But... on one hand it talks

It seems a bit of a lazy article to me. So apologies but my reply is only brief and I am not going to spend a lot of time on it... But... on one hand it talks about programmers making 15-20 common mistakes. Fine create a checklist for these issues. And then at number 1 it asks "does the code work?". Of course it's common that the code doesn't work, but it may not be a binary decision - requirements ambiguity, corner cases, dependent on data, etc. I have also have issues about the Documentation section - none of that will necessarily help "Stop more bugs"... I don't see the purpose of the article is clear and I don't think it's particularly consistent between the title, checklist and explanatory paragraphs.