|
I think there are only two things I can say of value here:
1. Over time the rating of an article levels out to a reasonably good approximation of its value. Please be patient. I know it sucks sometimes though.
2. Not all votes are equal. Votes from Silver, Gold and Platinum members all count for more (in increasing order) than those from other members. A 1 vote from a drive-by will quickly be repaired by a 4 or 5 from a solid member.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Thanks Chris, didn't know the votes were weighted. That does help. A little bit
|
|
|
|
|
Unless you manage to piss of a whole range of people elsewhere on the site.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Don't be fooled by rating. The amount of e-mail feedback I get from 4.0 (or even 3.9) articles (I have 2 such) tells me that people can read & think.
Your article will find it's reader regardless of the rating.
Right now I have 4 articles being written, and it is interesting to me to meet the challenges of programming and describing the whole thing in the article, not the rating I'll get
P.S. The most successful article here - ToDoList - has a rating of 4.75. Not 5, not 4.9...
-------------------------
Don't worry, be happy  )
|
|
|
|
|
I agree Dmitry, all good points.
But I think I'd be happier without any rating at all, is all I'm saying in the end. That way we wouldn't have to think thoughts like "don't be fooled by the rating" and "regardless of the rating" and "even 3.9" (I've done worse, by the way, with my first article, but in my case the rating was deserved).
Failing that:
In statistics (personally I'm allergic to it), when there's obvious and strong noise in a smallish sample it's a common practice to throw out the few highest and lowest data points to compensate. Some rare people will give you a 5 just for showing up. Others, if God appeared before them in person and made them pretty they might consider handing out a 3.
|
|
|
|
|
From the point of view of a writer I can certainly understand that you are put off by low votes. From the perspective of a reader the vote does guide me as to whether the article is worth reading or not.
Now, if an article has few votes I tend to ignore the actual vote as it is too early to say. Once it has about 5 to 10 votes I start to pay more attention. If it has over 25 votes I take the value as being a fairly accurate estimate of the articles worth.
So, what is the vote worth to me, as a reader?
4.0 to 5.0: I count that as a must read.
3.0 to 4.0: It is worthwhile reading, but I expect the odd gap here or there.
2.5 to 3.0: It may contain useful information but will most likely require supplimental reading to get what I want.
2.0 to 2.5: It possibly has what I want but will be so poorly written that it will require major effort to get to it.
1.0 to 2.0: The article will be so badly written that it isn't worth the effort to even try and read it.
|
|
|
|
|
Colin,
I've bookmarked your post. It is a real Reader's Guide to CodeProject!
-------------------------
Don't worry, be happy  )
|
|
|
|
|
Nice guide, thanks. I will pound your criteria into my head. Ouch ouch ouch.....
One final thought, then I'm outa here before I'm called 'the vote guy': most people don't vote. Not even one in a thousand it seems. Odd, that, are we all such a shy passive bunch?
|
|
|
|
|
Of course, you have to change your vote analysis when considering *my* articles. People vote mine down just for the sheer enjoyment of doing so. I have some articles that are down in the 2.0-2.8 range that are decent articles, but that were hammered by morons that can barely function on their own. Whoops, there I go again.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
kenearle wrote: Some thoughts in my head after watching the early responses to my "Custom ToolTips for MFC Projects"
I just looked at your profile. I don't see any articles there. Did you post under a different username?
|
|
|
|
|
Yeah, seems I'm Ken Earle[^] for articles, even though I submit with a username of 'kenearle' in my contacts info. Ah well, nice to have an alias I suppose.
|
|
|
|
|
I've moved the articles to your kenearle account.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
|
The voting system has been fundamentally broken since it was first initiated and has been complained about on a regular basis with no action taken despite many good suggestions. As the system stands now if you have anything over a 4 it's about the best you can hope for.
However that being said I just noticed that Chris has added weighting to the votes which is a good improvement so some action has been taken obviously, I retract what I said above  , however I really like Colin's statement that when an article has few votes you can't go by the score, that should be pursued as a feature: perhaps an article with less than 10 votes doesn't show it's score until the 11th onward or something.
I also think it would useful if people were more strongly encouraged to leave a comment if they vote significantly different than the current average.
"110%" - it's the new 70%
|
|
|
|
|
We've had many suggestions on the voting system but very few that are practical.
Weighted votes have been with us for years and tend to even out an article's rating over time faster than straight votes. The other suggestions we've had are:
- Showing a histogram (Like it, and am looking into incorporating it)
- Allowing members to change votes (this is being added)
- Forcing a comment (means we just get "asdf" comments)
- Restricting votes to N per day (people just create fake accounts)
- Displaying a list of who voted (this will just cause voting wars)
We also disallow votes from those not logged in, and disallow multiple votes from the same IP to make it harder for people to create fake accounts.
I'm open to more suggestions.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Hi Chris you must have missed my almost immediate edit on my message. I made two suggestions: don't show the score until a certain number of votes have been made, i.e. not until the 11th vote or something. This calms the author and doesn't skew the initial results.
The second is that any votes that are extremely off the current average should have a *Suggestion* pop up that they make a comment of why they voted that way.
"110%" - it's the new 70%
|
|
|
|
|
John Cardinal wrote: Hi Chris you must have missed my almost immediate edit on my message. I made two suggestions: don't show the score until a certain number of votes have been made, i.e. not until the 11th vote or something. This calms the author and doesn't skew the initial results.
If doing this it should be X votes or Y days so that an article that gets very few votes will eventually show a score.
--
CleaKO The sad part about this instance is that none of the users ever said anything [about the problem].
Pete O`Hanlon Doesn't that just tell you everything you need to know about users?
|
|
|
|
|
Anything that forces a suggestion will often result in either asdf or something that will get filtered out by our obscenity filter.
I've also toyed with the idea of using statistics to weed out poor votes but it's a tricky one. Let's say you have someone who creates 5 fake accounts and votes 5 5's. Someone else comes along and gives a more accurate "1". Statistically the 1 vote should be removed.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris Maunder wrote: Anything that forces a suggestion will often result in either asdf or something that will get filtered out by our obscenity filter.
Exactly. Which is why I capitalized and put asterisks around the word *Suggests* as in a wild vote deserves a popup suggesting the user make a comment, not forcing them to make a comment.
"110%" - it's the new 70%
|
|
|
|
|
Chris Maunder wrote: Statistically the 1 vote should be removed.
If someone's using fake accounts to skew the score, the stats are gonna be screwed up no matter what you do.
IMHO, a histogram is still the best bet for making the score more meaningful. You're actually presenting more information. If someone's gaming the system, well, the results are gonna be wrong regardless, but if you see an article with 2 1s and 5 5s and a weighted average of 3, you'll at least have a better clue of what's really going on...
----
It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.
--Raymond Chen on MSDN
|
|
|
|
|
John Cardinal wrote: don't show the score until a certain number of votes have been made, i.e. not until the 11th vote or something
Oooh, I like that, but I think the number should be higher, like say... 20 votes.
John Cardinal wrote: The second is that any votes that are extremely off the current average should have a *Suggestion* pop up that they make a comment of why they voted that way.
I think showing votes accumulated like this would alleviate Chris' voting wars fears (illustrating the way it would look for one of my articles - grin):
Vote -------------- Votes By -----------------
Value Platinum Gold Silver Bronze
5 1 4 2 3
4 5 2 7 0
3 0 0 5 0
2 0 0 0 0
1 0 0 1 4,038,764,324
Further, Chris cited the a probability that if forced to leave a comment, many folks would just post "asdf" or other equally invalid comments. My response was that a rudimentary text parser could be created that would parse the comment, and automatically reject votes that are associated with comments that failed the following checks:
a) When trimmed of leading and trailing spaces, did not contain any characeters. The nefarious "empty" comment.
b) Comments must have X number of characters (this prevents the simple "asdf" example provided by Chris. I would think 30 characters would be enough.
c) Comments that don't contain a certain percentage of spaces. Statistically speaking, Chris (or whoever) could take a reasonably long sentence out of a well-written article, and calculate the percentage of spaces in that sentence as a baseline.
d) If the comment passes all of the previous validation, come up with a vocabulary file and compare all of the words in the comment against it. Assign levels of coherence based on the percentage of word matches achieved and an ultimately lowest acceptable value that can be used to automatically reject the comment/vote pair as invalid.
So, if a comment matched 80-100% of its words with the vocabulary, it would be automatically labeled as "probably valid", and the vote/comment would be viewable by the article author who could then read it. The article author would be able to see the vote, the comment, and the member status (platinum, gold, etc), but would NOT be able to see who the person was that voted. Keep in mind that site admins WOULD be able to see who the vote came from and could take action behind the scenes to correct any problems with the voter (those who continue to perform drive-by-1's for no reason other than to cause havoc).
Notes:
The vocabulary file could be automatically created by selecting a handful of articles and parsing the text into file. Spell-check the file, and then move the words into a database table. That should cover the majority of words that might be used in a comment and would present a reasonably small vocabulary to prevent undue load on the server's CPU cycles. I figure a reasonable vocabulary would contain between 2000 and 3000 words since we're only looking for a percentage of matches.
A cleverly-constructed vocabulary list should further mitigate the server load issue.
If the comment is restricted to something like 120 characters, this will limit the number of words the voter can type, and would further reduce the server load during the vocabulary check.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
I have been accumulating notes on some of the software utilities I use regularly, and wanted to submit some reviews of this software to CP. I was surprised to find there is no Software Reviews section, although there is a Hardware Reviews under General Reading.
My suggestion: create a Software Reviews section under General Reading.
-- modified at 10:49 Saturday 14th April, 2007
Here are some possible subsections:- Backup
- Database
- Dev Tools
- Editors
- Email, RSS, & News Readers
- File Management
- IDE
- Media Players & Management
- PIM & Calendar
- Project Management
- Source Control
The general idea of a "software review" is to describe the main features, possibly compare several products, and show how to use it. Both free and non-free products could be discussed.
|
|
|
|
|
Has anyone else noticed that two entire threads, not just a post hear or there in them, have disappeared from the Coding Horrors forum?
Did they actually get removed or moved somewhere else?
Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007
|
|
|
|
|
There were two threads that were removed.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
How about only being able to vote when actually replying?
V.
I found a living worth working for, but haven't found work worth living for.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
