Why should we bother to rate and comment,?
-
Original Article that made me write this[^][^] ( scroll to the comments :P) First and foremost anyone who writes an article and puts effort into, reads the guidelines, and makes a serious attempt and a 5 star article deserves at least 3 stars. Anyways, the thing is this community is about providing quality material to professional programmers and we do this through community contributions. The side effect is not every article is going to be great and at the same time authors need to be able to take criticism and use that productively to either improve the article or apply it to the next submission. Summary: If you're going to get hurt because someone said your article needs work then please refrain from submitting. Criticism is the core of this community and if you cant take the heat get out of the kitchen.
I think you missed the fact that it had not been approved yet - and you now have access to these articles. Your comments were exactly what is expected and should be appreciated, the article is basically a code dump with little explanation. I can't see where the author had a problem with your criticism, seemed like the start of a sensible discussion to me. His goal on the article was badly explained and you assumed a different goal. Dragging it into the Lounge seems a little harsh.
Never underestimate the power of human stupidity RAH
-
Josh_Jackson wrote:
Fair enough, in the future I'll hand out higher scores. It's simply that like you said the archive has quite a few horrors that need to have proper ratings and proper criticism. I've handed out my apology to the author and revise my rating and then move on.
Okay, perhaps my reply to you was a little unnecessarily rude as well. I am sorry about that. I can see that you were trying to help the author. When I 1-vote an article I usually mean, "this article needs to be deleted immediately.". It's my way of telling the site admins that the article needs to be nuked. If I think an article can be improved, I usually vote a 3 and then give some advice. Nowadays I just give my suggestions - I don't vote at all. I know all this is subjective and that different people use the rating system differently. I also noticed that you are still in school. For someone that young, you have certainly replied to me in a very mature manner. :thumbsup:
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
Thank you Nish, simply put I don't want to drive people away only to try to help, which I may not always do in the most tactful or "best" way, and sometimes my tongue runs astray. I do believe that in the future Ill withhold ratings and provide feedback in a more positive manner. :D
modified on Tuesday, August 10, 2010 8:55 PM
-
Uhhh, lol strange last time I check I was a lowly peon...
The threshold probably got lowered again from gold to silver authorship. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
Original Article that made me write this[^][^] ( scroll to the comments :P) First and foremost anyone who writes an article and puts effort into, reads the guidelines, and makes a serious attempt and a 5 star article deserves at least 3 stars. Anyways, the thing is this community is about providing quality material to professional programmers and we do this through community contributions. The side effect is not every article is going to be great and at the same time authors need to be able to take criticism and use that productively to either improve the article or apply it to the next submission. Summary: If you're going to get hurt because someone said your article needs work then please refrain from submitting. Criticism is the core of this community and if you cant take the heat get out of the kitchen.
I think your comments and his reply were both fairly civilized, but I think your vote of 1 was pretty harsh. Believe me, I've seen plenty of submissions that well deserve a 1 vote, but in my opinion, this one didn't. Since the article wasn't approved yet, I would have refrained from voting and just left the comment without a vote. That way the author has a chance to edit, etc.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
I think your comments and his reply were both fairly civilized, but I think your vote of 1 was pretty harsh. Believe me, I've seen plenty of submissions that well deserve a 1 vote, but in my opinion, this one didn't. Since the article wasn't approved yet, I would have refrained from voting and just left the comment without a vote. That way the author has a chance to edit, etc.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
Yes, perhaps bringing it up in the lounge was a bit much but my intentions where to simply bring up the topic in a place that would receive attention and call forth the fact that constructive criticism is not meant to be a personal attack but informative and helpful. Do believe I'll keep these things between me and the affected individual from now on.
-
Original Article that made me write this[^][^] ( scroll to the comments :P) First and foremost anyone who writes an article and puts effort into, reads the guidelines, and makes a serious attempt and a 5 star article deserves at least 3 stars. Anyways, the thing is this community is about providing quality material to professional programmers and we do this through community contributions. The side effect is not every article is going to be great and at the same time authors need to be able to take criticism and use that productively to either improve the article or apply it to the next submission. Summary: If you're going to get hurt because someone said your article needs work then please refrain from submitting. Criticism is the core of this community and if you cant take the heat get out of the kitchen.
I never bother to rate or comment any article anymore except when the article is very good. So I only vote 5 or do not vote at all. I was tired by the extremely poor articles that appeared on this site (the article in question is very good compared to those articles)
Josh_Jackson wrote:
Criticism is the core of this community
That’s not at all true! The fact is that extremely few authors (probably < 5 on this site which has thousands of authors) can actually take criticism of any kind unless it is veiled in a praise. This is understandable as an author spends lot of time writing an article and the last thing he wants to hear is that the article is sub-standard. My policy is simple :- 1. Do not criticize an article unless you know the author very well and he is a personal friend. 2. Do not criticize someone unless who you think might not be receptive to criticism (virtually every new author or an author whom you have not praised :) ). Your time is better spent not arguing. 3. If an author asks you to review/criticize then by all means criticize the article (not him :) ).
-
Original Article that made me write this[^][^] ( scroll to the comments :P) First and foremost anyone who writes an article and puts effort into, reads the guidelines, and makes a serious attempt and a 5 star article deserves at least 3 stars. Anyways, the thing is this community is about providing quality material to professional programmers and we do this through community contributions. The side effect is not every article is going to be great and at the same time authors need to be able to take criticism and use that productively to either improve the article or apply it to the next submission. Summary: If you're going to get hurt because someone said your article needs work then please refrain from submitting. Criticism is the core of this community and if you cant take the heat get out of the kitchen.
Josh_Jackson wrote:
Criticism is the core of this community
no it isn't
-
Josh_Jackson wrote:
Criticism is the core of this community
no it isn't
Ok, lets change it to "criticism should be core to improving the quality of articles for the community"? lol
-
Original Article that made me write this[^][^] ( scroll to the comments :P) First and foremost anyone who writes an article and puts effort into, reads the guidelines, and makes a serious attempt and a 5 star article deserves at least 3 stars. Anyways, the thing is this community is about providing quality material to professional programmers and we do this through community contributions. The side effect is not every article is going to be great and at the same time authors need to be able to take criticism and use that productively to either improve the article or apply it to the next submission. Summary: If you're going to get hurt because someone said your article needs work then please refrain from submitting. Criticism is the core of this community and if you cant take the heat get out of the kitchen.
I seem to recall a very similar article a few weeks back, but I haven't been able to locate it. Edit: Here it is[^]. He has improved it somewhat.
-
I seem to recall a very similar article a few weeks back, but I haven't been able to locate it. Edit: Here it is[^]. He has improved it somewhat.
Now I understand why he is showing lots of code... :laugh:
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
-
Now I understand why he is showing lots of code... :laugh:
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
Luc Pattyn wrote:
Now I understand why he is showing lots of code...
:-D
Regards, Nish
Blog: blog.voidnish.com Most recent article: An MVVM friendly approach to adding system menu entries in a WPF application
-
Now I understand why he is showing lots of code... :laugh:
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum
Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.
Now he will come up with another version with less code :).