Sometimes it is easy to decide if you want to help an author improve his article. Or not. When you see an article with most of the boilerplate intact, or with only a few sentences and a download, then you know the author really didn't care, and so why should you? But when you see an article with a lot of details, with some attempt at explanation, with screenshots, then you want to take a closer look; this could be a great article, if only the author would do a few things...
Rules of Engagement
What do I look for? Here are some of the things:
- Could this article be useful to someone? If the article just repeats what anyone could find on MSDN with a google search, then the answer is probably no. But if the article talks about how to apply some API or framework feature, or explains it in a way that MSDN does not make clear, then the answer is probably yes.
- Do you remember having to look for this information yourself? Sometimes there are things that just take a while to find, and after that you just "know" them. Finding them is the tough bit. If the article can help save time for someone, then it's got a go from me, even if it's about something trivial.
- Does the article state a problem and then show how to solve it? No matter what the problem is, if the author demonstrates how he worked through it and came up with an answer, by definition that is what an article should do. Easily a go.
- Does the article explain some non-trivial technology? Unless there are other and better articles on CodeProject that discuss the same technology, I would be inclined to take the article seriously. Even if the same technology is described in other articles, the author might have a different take on it, or show how it can be used in different ways. (Have you seen how many color pickers we have?)
If you feel the article falls just short of what would make a good article, tell the author so, and tell him why. With a different approach, or by including more details, would the article be acceptable? Tell the author about the way you see things, and give suggestions if you think the article is salvageable. In a positive way, of course.