A sad statement of our community
-
Nic Rowan wrote:
To be honest I think the only way to curb drive-by 1 voting is to record who voted for the guy and display it.
A while back, David Stone posted a link to a "Sparklines"-style score display - essentially, you get a line-graphed histogram rather than a simple weighted average. I'd love to see something like that, both for articles and posts. IMHO, it would greatly reduce the temptation to use 1 and 5 exclusively ("the score's lower than it should be, i'll vote higher than it deserves to compensate"), while reducing the perceived impact of a single low / high vote.
----
...the wind blows over it and it is gone, and its place remembers it no more...
I quite like the voting display on MSDN - i.e. a bar for each number 1-9. It takes up too much room, but you can see the total or relative number of votes for each bar.
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.
-
Thank you very much for your kind words. Stuff like this is what drives me to keep writing articles, in spite of people that vote 1 without saying why. I know I'm not perfect, actually, far from it, and with this being my first article, I hoped for a lot of comments on how should I improve it, but when I got that vote, it really turned me down. Again, thank you and the others for your words, and know that I will continue writing. CP has helped me a lot, and, if I can help a little, then I'll be glad to do it. And yes, i'm from Argentina, a spanish-speaking country, but I always liked english more than spanish. Matias Szulman
I gave it a 5 for the reasons John already provided. I was keenly impressed by the fact you churned out a result given such a loose spec provided what... a day prior? I think doing something like that embodies the spirit of CP as much anything else if not more. You demonstrated initiative outside of your own problem area and published a sample that will no doubt inspire others to pick up and carry on. That's CP in my opinion. I think you should us something in your initial action that is of much higher value than we showed you in response to Marc's alerting us to the issue at hand.
My name is Maximus Decimus Meridius, Commander of the Armies of the North, General of the Felix Legions, loyal servant to the true emperor, Marcus Aurelius. Father to a murdered process, husband to a murdered thread. And I will have my vengeance, in this life or the next. - Gladiator I work to live. I do not live to work. My clients do not seem capable of grasping this fact.
-
I quite like the voting display on MSDN - i.e. a bar for each number 1-9. It takes up too much room, but you can see the total or relative number of votes for each bar.
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.
(i didn't realize we could vote on MSDN - care to share a link to what you're talking about?)
Ashley van Gerven wrote:
a bar for each number 1-9. It takes up too much room, but you can see the total or relative number of votes for each bar.
That makes more sense for an article, where you have a lot of space. Still, it shouldn't be necessary to know at a glance exactly how many people voted each level - a quick glance will tell you that (say) roughly 50% of the total voted 4, 10% voted 5, etc. When there are just a handful of total votes, a bar graph would pretty much tell you how many people voted each #. For a larger number, both line and bar graphs still give you a good "at a glance" feel for how the article is perceived. Numbered bars would excel in one category though - "vote this post" polls... ;)
----
...the wind blows over it and it is gone, and its place remembers it no more...
-
(i didn't realize we could vote on MSDN - care to share a link to what you're talking about?)
Ashley van Gerven wrote:
a bar for each number 1-9. It takes up too much room, but you can see the total or relative number of votes for each bar.
That makes more sense for an article, where you have a lot of space. Still, it shouldn't be necessary to know at a glance exactly how many people voted each level - a quick glance will tell you that (say) roughly 50% of the total voted 4, 10% voted 5, etc. When there are just a handful of total votes, a bar graph would pretty much tell you how many people voted each #. For a larger number, both line and bar graphs still give you a good "at a glance" feel for how the article is perceived. Numbered bars would excel in one category though - "vote this post" polls... ;)
----
...the wind blows over it and it is gone, and its place remembers it no more...
Well it seems MSDN 2 is using an average rating system: http://msdn2.microsoft.com/en-us/library/system.timezone.aspx. But they used to have a bar graph (can't recall which MSDN section(s) tho). Seems we're on the same wavelength as Chris... he's planning a 'histogram[^]' by the looks of it - didn't know that's what it was called.
"For fifty bucks I'd put my face in their soup and blow." - George Costanza
CP article: SmartPager - a Flickr-style pager control with go-to-page popup layer.