Rating question
-
Hello everybody, have a look at this article: http://www.codeproject.com/useritems/FileGlob.asp[^] It's rating is 4.6, and 2 users have rated this article... how's that possible??? 4.5 would mean, that one user gave it a 5 and the other one gave a 4. But 4.6 ??? :-D -Dominik
-
Hello everybody, have a look at this article: http://www.codeproject.com/useritems/FileGlob.asp[^] It's rating is 4.6, and 2 users have rated this article... how's that possible??? 4.5 would mean, that one user gave it a 5 and the other one gave a 4. But 4.6 ??? :-D -Dominik
I have read in the "suggestions salon" that the actual vote figure depends on your profile. One with gold, silver, and so on will not have the same value than someone who votes being just logged on. This is a fair enough reason for that 4.6!
And I swallow a small raisin.
-
Hello everybody, have a look at this article: http://www.codeproject.com/useritems/FileGlob.asp[^] It's rating is 4.6, and 2 users have rated this article... how's that possible??? 4.5 would mean, that one user gave it a 5 and the other one gave a 4. But 4.6 ??? :-D -Dominik
your vote is weighted depening on your status, bronze vote is not worth as much as a platinums vote. so u better stay in nish's good books :rolleyes:
:suss: Email: theeclypse@hotmail.com URL: http://www.onyeyiri.co.uk
:suss:"All programmers are playwrights and all computers are lousy actors." -
Hello everybody, have a look at this article: http://www.codeproject.com/useritems/FileGlob.asp[^] It's rating is 4.6, and 2 users have rated this article... how's that possible??? 4.5 would mean, that one user gave it a 5 and the other one gave a 4. But 4.6 ??? :-D -Dominik
yeah but who actually votes anyway? I vote on articles I use - but I don't vote on an article I have just skimmed over. Maybe I should vote more :)
Stupidity dies. The end of future offspring. Evolution wins. - A Darwin Awards Haiku
-
Hello everybody, have a look at this article: http://www.codeproject.com/useritems/FileGlob.asp[^] It's rating is 4.6, and 2 users have rated this article... how's that possible??? 4.5 would mean, that one user gave it a 5 and the other one gave a 4. But 4.6 ??? :-D -Dominik
Thanks, this makes sense... :-O
-
yeah but who actually votes anyway? I vote on articles I use - but I don't vote on an article I have just skimmed over. Maybe I should vote more :)
Stupidity dies. The end of future offspring. Evolution wins. - A Darwin Awards Haiku
Shaun Wilde wrote: Maybe I should vote more No I think your way is good. By actually going through the motions of using an articles code you really explore how good the article and code is. Awhile back I voted an article quite highly after having just read it. However a month later I actually had a chance to use the code and apply what the article taught me. That is when I realised the article did not deserve such a high rating as it missed out on explaining some key concepts to using the code. It was still good, just not as good as I thought after that one read. Just like my rating of a real world product I have never used/bought is not worth much. regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
-
Shaun Wilde wrote: Maybe I should vote more No I think your way is good. By actually going through the motions of using an articles code you really explore how good the article and code is. Awhile back I voted an article quite highly after having just read it. However a month later I actually had a chance to use the code and apply what the article taught me. That is when I realised the article did not deserve such a high rating as it missed out on explaining some key concepts to using the code. It was still good, just not as good as I thought after that one read. Just like my rating of a real world product I have never used/bought is not worth much. regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
Since voting for an article does not have any obligations, neither it gives any commercial advantages to the writer, I think it's fine to vote often, even if you didn't actually use the article in your development. Voting is just a way to motivate (or criticize) people who take their time and bring their knowledge to others. Vagif Abilov MCP (Visual C++) Oslo, Norway If you're in a war, instead of throwing a hand grenade at the enemy, throw one of those small pumpkins. Maybe it'll make everyone think how stupid war is, and while they are thinking, you can throw a real grenade at them. Jack Handey, Deep Thoughts
-
Shaun Wilde wrote: Maybe I should vote more No I think your way is good. By actually going through the motions of using an articles code you really explore how good the article and code is. Awhile back I voted an article quite highly after having just read it. However a month later I actually had a chance to use the code and apply what the article taught me. That is when I realised the article did not deserve such a high rating as it missed out on explaining some key concepts to using the code. It was still good, just not as good as I thought after that one read. Just like my rating of a real world product I have never used/bought is not worth much. regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
I think that depends on the article. For example an article that is a tutorial, can actually teach you without having to use the code. But a reusable class should be tested before it's rated. However many articles here at CP fall in between the two types so they can be rated by different people for entirly different reasons. Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
-
I think that depends on the article. For example an article that is a tutorial, can actually teach you without having to use the code. But a reusable class should be tested before it's rated. However many articles here at CP fall in between the two types so they can be rated by different people for entirly different reasons. Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
Colin^Davies wrote: For example an article that is a tutorial, can actually teach you without having to use the code Sorry I did not explain myself clearly. Basically I think one should only rate an article once you have used it (the article and if code is provided, then the code too.) If it is a tutorial then by using I mean going through it and actually doing what the tut. says. Building the project, writing the code, testing etc. I read quite a few articles, but mainly on a superficial level. If the article seems useful then I bookmark it. Then when the time comes that I actually need the article I will read and use it as best I can. Then I rate it. Sometimes the gap can be a week, sometimes a few months, all depends on what I am working on. Colin^Davies wrote: can be rated by different people for entirly different reasons. I do appreciate the effort and time people put into their articles. However when I rate an article I am rating it not for myself, but so as to indicate to others that this article is worth something. So if I rate based on how much I like the author, or the fact they write well, then I am not doing a good "job" of rating. If I rate based purely on usefulness then I feel the rating is worth something to others. There have been some articles which have terrible English, poor layout and the demos don't work (hey, sounds like my article :-D) but which have proven very useful. So I rated them well. Bottom line for me is: Is the article useful? Naturally if it is a tutorial then the usefulness aspect comes from how well the author leads you through the tutorial. In that case well written definitley helps. It tough trying to find a rule that works well for all articles, but usefulness is as close as I have gotten :) * Obviously a well written AND useful article is even better, but if I had to choose between the two then I would choose usefulness regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
-
Colin^Davies wrote: For example an article that is a tutorial, can actually teach you without having to use the code Sorry I did not explain myself clearly. Basically I think one should only rate an article once you have used it (the article and if code is provided, then the code too.) If it is a tutorial then by using I mean going through it and actually doing what the tut. says. Building the project, writing the code, testing etc. I read quite a few articles, but mainly on a superficial level. If the article seems useful then I bookmark it. Then when the time comes that I actually need the article I will read and use it as best I can. Then I rate it. Sometimes the gap can be a week, sometimes a few months, all depends on what I am working on. Colin^Davies wrote: can be rated by different people for entirly different reasons. I do appreciate the effort and time people put into their articles. However when I rate an article I am rating it not for myself, but so as to indicate to others that this article is worth something. So if I rate based on how much I like the author, or the fact they write well, then I am not doing a good "job" of rating. If I rate based purely on usefulness then I feel the rating is worth something to others. There have been some articles which have terrible English, poor layout and the demos don't work (hey, sounds like my article :-D) but which have proven very useful. So I rated them well. Bottom line for me is: Is the article useful? Naturally if it is a tutorial then the usefulness aspect comes from how well the author leads you through the tutorial. In that case well written definitley helps. It tough trying to find a rule that works well for all articles, but usefulness is as close as I have gotten :) * Obviously a well written AND useful article is even better, but if I had to choose between the two then I would choose usefulness regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
Paul Watson wrote: Bottom line for me is: Is the article useful? I can't disagree with that. Paul Watson wrote: There have been some articles which have terrible English, poor layout and the demos don't work Seriously "Blame the editors not the authors." Paul Watson wrote: but usefulness is as close as I have gotten I thought that word was filtered :-) Regardz Colin J Davies
Sonork ID 100.9197:Colin
You are the intrepid one, always willing to leap into the fray! A serious character flaw, I might add, but entertaining. Said by Roger Wright about me.
-
Since voting for an article does not have any obligations, neither it gives any commercial advantages to the writer, I think it's fine to vote often, even if you didn't actually use the article in your development. Voting is just a way to motivate (or criticize) people who take their time and bring their knowledge to others. Vagif Abilov MCP (Visual C++) Oslo, Norway If you're in a war, instead of throwing a hand grenade at the enemy, throw one of those small pumpkins. Maybe it'll make everyone think how stupid war is, and while they are thinking, you can throw a real grenade at them. Jack Handey, Deep Thoughts
Vagif Abilov wrote: Voting is just a way to motivate (or criticize) people who take their time and bring their knowledge to others. I believe that is what the Comments section is for. Rating to me is a way to quickly highlight those articles of worth to others. So out of 1 billion articles, people can easily see which are useful and which aren't. Obviously rating also motivates the authors, but that IMO should not be your intent when rating an article. If you want to encourage, criticise etc. the author then write a comment. Bottom line for me: Rating is based on the usefulness of the article. Whether it be an article containing useful code or an article containing a useful set of steps to achieve something. But that is just my take :) Personally I think there should be four or so "subjects" for rating, and they add up to a total rating score. e.g. Choose 1 to 5 for; Well Written, Useful Code etc. etc. That way we can see what the article was rated well for. Is it a well written article but the code is not that helpful? Or is the code brilliant but the article text itself rather poor. etc. regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
-
Hello everybody, have a look at this article: http://www.codeproject.com/useritems/FileGlob.asp[^] It's rating is 4.6, and 2 users have rated this article... how's that possible??? 4.5 would mean, that one user gave it a 5 and the other one gave a 4. But 4.6 ??? :-D -Dominik
Did you see it right ? Blink ;) Ragavendran Vaidhyanadhan
-
yeah but who actually votes anyway? I vote on articles I use - but I don't vote on an article I have just skimmed over. Maybe I should vote more :)
Stupidity dies. The end of future offspring. Evolution wins. - A Darwin Awards Haiku
Shaun Wilde wrote: I vote on articles I use - but I don't vote on an article I have just skimmed over. Maybe I should vote more I think you use the correct approach... as I do. I only vote on articles that use or read to get some info. Mauricio Ritter - Brazil Sonorking now: 100.13560 MRitter :jig: I've gone sending to outer space, to find another race :jig:
-
your vote is weighted depening on your status, bronze vote is not worth as much as a platinums vote. so u better stay in nish's good books :rolleyes:
:suss: Email: theeclypse@hotmail.com URL: http://www.onyeyiri.co.uk
:suss:"All programmers are playwrights and all computers are lousy actors."Nnamdi Onyeyiri wrote: your vote is weighted depening on your status, bronze vote is not worth as much as a platinums vote Cool. Well I may not be a platinum member, but use of my voting abilities starts at $5 per article... ;)
David Wulff http://www.davidwulff.co.uk
I'm not schizophrenic, are we.
-
Vagif Abilov wrote: Voting is just a way to motivate (or criticize) people who take their time and bring their knowledge to others. I believe that is what the Comments section is for. Rating to me is a way to quickly highlight those articles of worth to others. So out of 1 billion articles, people can easily see which are useful and which aren't. Obviously rating also motivates the authors, but that IMO should not be your intent when rating an article. If you want to encourage, criticise etc. the author then write a comment. Bottom line for me: Rating is based on the usefulness of the article. Whether it be an article containing useful code or an article containing a useful set of steps to achieve something. But that is just my take :) Personally I think there should be four or so "subjects" for rating, and they add up to a total rating score. e.g. Choose 1 to 5 for; Well Written, Useful Code etc. etc. That way we can see what the article was rated well for. Is it a well written article but the code is not that helpful? Or is the code brilliant but the article text itself rather poor. etc. regards, Paul Watson Bluegrass Cape Town, South Africa Simon Walton wrote: "You come across a lot of people who call themselves realists, when they are actually pessimists attempting to look intelligent."
Paul Watson wrote: I believe that is what the Comments section is for. Rating to me is a way to quickly highlight those articles of worth to others. So out of 1 billion articles, people can easily see which are useful and which aren't. Obviously rating also motivates the authors, but that IMO should not be your intent when rating an article. If you want to encourage, criticise etc. the author then write a comment. I can't disagree with this. However, I assume that most of the people who read article don't vote. So I don't see anything wrong with leaving my rating after quick content examination. I compensate for those who will use the article and forget to vote :) Vagif Abilov MCP (Visual C++) Oslo, Norway If you're in a war, instead of throwing a hand grenade at the enemy, throw one of those small pumpkins. Maybe it'll make everyone think how stupid war is, and while they are thinking, you can throw a real grenade at them. Jack Handey, Deep Thoughts