|
I think and article should be rated for:
1) Uniqueness or usefulness idea.
2) How well the article is written. Does he explain what he is doing? How & why?
3) How clear or concise is the idea being conveyed?
4) Is there sample code? And some kind of picture or diagram? (where applicable)
5) Is the idea a good way to perform what the author claims?
The "ExCB - Extended Multi Column ComboBox" is a excellent control. Definitely a great addition to codeproject. But it lacks explanation, and content in the article. How did he do what he is creating an article about? Why did he do things the way he did? Only code available is only related to how to use the control, basically documentation.
"Better to ask for forgiveness then permissions" is a good well written article. But looking at the code it does not seem to be the most efficient way of achieving this goal. And the actual usage of the application is trivial. As we can easily go into properties and change permissions. This does not seem to offer any advantages of changing permissions vs the traditional way. If anything it may over complicate things.
"Fun with Sound" not only hits all the above points, but he also included sample code in more than 1 language. A big plus for many. However, unless you are developing a game, i cant imagine playing a multitude of sounds and over lapping them. But none the less it's a great article and idea.
"Load More Records in ASP.NET Gridview on Button Click from SQL Server Table" also hits all the key points mentioned before, also offers sample code in different languages and i can definitely see used in a real world application. Especially with how the web is changing and more content is being created & updated dynamically. He provided something useful for everyday use, took the time to create, outline and explain his article. Those qualities should be (imho) what more articles should contain.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
