> It's generally much more helpful to say what's correct than what's wrong, if only because there are so many more ways to be wrong. So you should know what is

> It's generally much more helpful to say what's correct than what's wrong, if only because there are so many more ways to be wrong. So you should know what is correct before pointing out what is wrong? That doesn't sound right. > Getting rid of a flawed but workable model without having a better one to replace it with is not an improvement. This ignores the opportunity gained from not doing something. If "Myth Lists" aren't worth doing, not doing them is an improvement. You don't need to have a "better alternative", because "doing nothing" is already better. Having said that, the article doesn't exactly show that Myth Lists don't work. It's just an opinion of someone who read one of these lately and didn't like it.