|
If something is genuinely helpful or educational I upvote on occasions.
But I seldomly downvote as it sometimes triggers a load of revenge voting. 
I'm going for the report button instead, but that also only on pure garbage.
Wrong is evil and must be defeated. - Jeff Ello
Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but assholes.
|
|
|
|
|
For me, a vote of 1 entails the article was totally irrelevant and added no technical value whatsoever, or was plagiarised.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Plagiarized or irrelevant should be reported so that they can be removed rather than just downvoted.
Downvotes are for bad code, or bad methodology.
Wrong is evil and must be defeated. - Jeff Ello
Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but assholes.
|
|
|
|
|
I don't anymore; I report it as poor quality or formatting or whatever.
The main problem with ratings is that voters rarely alter a vote once an article is improved.
|
|
|
|
|
It's pretty hard to change a report too.
Wrong is evil and must be defeated. - Jeff Ello
Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but assholes.
|
|
|
|
|
True, but if an article has been edited, the report counter is reset to 0. So if you want to undo a report after an article has been improved, then that's not necessary because it already is undone.
The quick red ProgramFOX jumps right over the Lazy<Dog>.
|
|
|
|
|
I remember my second article on CodeProject.
After my first (on Try Catch Finally) was a HUUUGEEEE success (well, I had about six months of programming experience and I got a few 5 votes) I decided to write a second.
My very own ORM (sort of, because after six months I had never heard of an ORM, or of anything other than Visual Basic and SQL Server for that matter).
I got a 1... And another and another... And then I got a message that, unfortunately, my article was removed because the quality was insufficient for CodeProject.
I learned two things that day. 1, There are such things as Object Oriented Programming, SOLID, Design Patterns, etc... And 2, people don't like to tell you what's wrong with your article in a civilized and constructive manner.
Luckily someone told me what was wrong with my article (after giving me a 1 and calling me names and after I politely asked what was wrong with it).
I can say I learned more from that crap article than from all my other articles combined. Sort of 
That said, I give a one vote if I feel the author has put time and effort in his article and wants to learn from it as well as educate others.
I don't like doing it because I know how it feels and if I do it I politely explain why I voted a 1 and encourage the author to carry on and improve his article.
It doesn't happen that often as I usually only read the good articles
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
My blog[ ^]
|
|
|
|
|
Turning a negative experience into a positive one. I like that 
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Actually I still cry myself to sleep at night! 
It's an OO world.
public class SanderRossel : Lazy<Person>
{
public void DoWork()
{
throw new NotSupportedException();
}
}
My blog[ ^]
|
|
|
|
|
Since the advent of moderation, I have found little use for the onesies. However, if and when I come across pure and utter drivel, one it gets and if it's spam or plagiarism I'll happily report it to boot.
|
|
|
|
|
I haven't given a 1 vote to any article. I would if it were outright plagiarism or if there were offensive material presented. I do feel that a 1 or a 2 vote for an article should not be allowed unless a comment with a reason is given. (I’m sure this has been brought up in Bugs and Sugs?)
I would add that the sting of a down vote should give an author reason to carefully consider what they present in the future.
It was broke, so I fixed it.
|
|
|
|
|
I give a one vote if the article is just written by someone who was obviously lazy about writing it. Outside of that I never vote a 1. In fact, I rarely vote a 2, 3, or 4. It's always either a 1 or 5.
Jeremy Falcon
|
|
|
|
|
I put 1 only on "articles" that are no more than a few sentences or a clear free publicity for some kind of tool. I also loathe the "articles" in which some basic idea is presented as a revolutionary enlightment, more so when it is poorly explained or realised.
|
|
|
|
|
Dominic Burford wrote: under what conditions would you give a very low mark to an article?
I agree. If the article is at least an attempt to be serious and create something then a one shouldn't have even made it through the quality checks.
I do have ONE BIG REQUIREMENT and I've seen it broken here on an article which tells you "why you should use an RSS reader" instead of how to DEVELOP one.
The Requirement
The article must explain something related to code: how to build, how to architect solutions and the patterns that go with it, how to configure (programmatically). These articles must be technically oriented and at least oriented toward a developer mindset. Some form of automation -- via programming should be considered. Some form of software development, even if it is writing a batch file.
AFter all, the call sign for the site is: CodeProject is "For those who code".
Of course, I am not saying Technical Blogs have to be directly related to code either and if the person marks the item as Blog then that is fine also. But for articles and tips, please keep them directly related to code.
And one more thing, I've never even voted a 1. I don't even want to bother to tell the person.
|
|
|
|
|
I don't think I have ever rated an article, maybe once, I prefer to leave comments as voting systems tend to become too 'political'.
|
|
|
|
|
Movie Quote Of The Day
Me, I can get blood out of a sock.
Which movie?
|
|
|
|
|
Blade IV: Time of the laundry
|
|
|
|
|
Any reality show involving male students and their laundry habits... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Interview With the Married Vampire
|
|
|
|
|
Bear Grylls the movie
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
|
The Walking Socks
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Cut the nails 
|
|
|
|
|
Bloody Sock for Dummies
OR
You Don't Mess With The Bloody Sock
Your time will come, if you let it be right.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
