Do something wrong, we notice. Do something right, we ignore.
-
I have have one article/blog post that gets almost daily downloads of the source but very few comments. I would like to think that if we have few comments then we have been very clear on the content of the article and left no or few questions unanswered. After reading articles for the last... umm how many years have I been here now. Any way the ones that get the most comments are the ones where people want to do more with the source than what was originally intended or have a problem with what it does when it runs, if they can get it to run. Or the upvotes with comments.
Thanks for chiming in on this thread. Tried out your Registry program on Windows 7, ran as admin and it worked great. That's a cool little utility that could be really helpful.
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
I got used to this model a long time ago. Primarily when working with software that is delivered directly to the customer. We never hear the kudos or anything positive come our way, even if we created something custom for the customer. You can be for damn sure you'll know when it's broken. No news is good news. Unfortunately that doesn't provide the votes and praise in the comments section of articles here. It's always good to get the feedback both positive and negative.
To know and not do, is not yet to know
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
This is perfectly understandable, a well written article deserves and usually gets a 5 as a thank you, whereas as crappy article needs some comment so the author can improve their skills. I consider the download counter as my thank you, they read the article and it sparked enough interest that they downloaded he code. Any upvote and comment is a bonus, appreciated but not the reason for writing an article. Negative comment on the other hand need to be addressed.
Never underestimate the power of human stupidity RAH
-
Thanks for chiming in on this thread. Tried out your Registry program on Windows 7, ran as admin and it worked great. That's a cool little utility that could be really helpful.
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
I was about to ignore this comment simply because I agree with you... So, I upvoted your message and I am posting this to let you know.
-
What would be the fun of humiliating someone that does something right?
VS2010/Atmel Studio 6.1 ToDo Manager Extension The problem with the gene pool is that there is no lifeguard. -Steven Wright
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
To paraphrase my granny: If you can't say something nice, STFU". I'm not sure that there's a comparable saw in the US -- denigrating others seems to be more acceptable, there.
I wanna be a eunuchs developer! Pass me a bread knife!
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
Blame it on Brits. They invented Tall Poppy Syndrome!!
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
"If it ain't broke, don't try to fix it." I'd guess it's because something done right has been done, finished, completed, works fine, not interesting any more. Something which is wrong needs fixing.
-
You haven't met my mother. The lady is an absolute bear about good manners. 'Please' and 'thank you' were the order of the day when I was growing up. As a middle-aged professional in a world that seems to turn ever more callous and self-interested, expressing my appreciation for someone else's hard work should be a reflex. I'm ashamed when it isn't. As far as the positivity goes, CP goes through cycles where the barbarian hordes run loose and bad behavior reigns. I've been guilty of it in the past. This is my favorite place on the web, so I'd rather not slip on my own spilled vitriol.
Software Zen:
delete this; -
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
newton.saber wrote:
So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge
I tend to read the article and often ignore the comments. I figure most CP authors are savvy enough that they address the comments that have been made in the article long before I get there. I come here to learn from others that know more than I do. I figure an author has done their best on an article, so if misspelled words, poor grammar and non-compiling code is what their article contains, then that's probably the best they can do and there might not be much I can learn from them.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
Reading 10,000 thank yous, greats and thnks for the codez, it's not very helpful at all, so i avoid such comments and better upvote the article to reflect i like it or that was really helpful.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
:-\ Welcome to CP :).
Software Zen:
delete this; -
:-\ Welcome to CP :).
Software Zen:
delete this; -
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
-
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly, had code samples that don't compile and wasn't well written, but it received numerous comments. Of course, they were mostly negative. It struck me afterward that if you do something right (write a terrific article), we may just download your code and ignore you. However, if you do something wrong (write a poor article) we are going to let you know. So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge. :) Do you find my topic interesting or even well thought out? You probably won't comment. However, if you eschew my point you will comment heavily. :-D Am I funny yet? I guess you can prove me wrong, easily, by being positive. I just played you, my friend. :cool: But, I'm serious. I feel a serious paradox coming on. :laugh:
newton.saber wrote:
Just read an article here at CodeProject (I shan't mention which) that was formatted poorly...
I won't EVER hold that against someone posting an article in Code Project. Their formatting tool ROYALLY SUCKS! Spent hours fighting the tool. Including throwing out the whole ball of wax and starting from scratch. I gave up in disgust. I was able to publish an article years ago, it was a pretty poor tool then, but you could get it to somewhat work OK. Either they've designed it to be worse, or I've gotten better at screwing it up. To criticize seems to be a human condition, especially when the "something" written is just wrong. There seems to be an unending supply of THAT on the web. Another web blog site had an article about the bubble sort. I went Ugh, but said to myself "It's a beginning author rehashing an inefficient process, that has been around forever. Leave the poor sap alone, doesn't have the background to know how bad the process is." Then I read a comment, praising the routine, how easy it was to understand and how efficient it was. That, I couldn't leave alone. I wrote a binary sort routine, test data, explained how inefficient the bubble sort was. (Every time you double the number being sorted, you quadruple the time it takes to sort.) I stopped testing the bubble sort at 200000 records because it was consistently quadrupling (or more) the time for double the ints in the array and 200K took 2 minutes 20 seconds to sort. The binary sort was still sorting in sub second times. I stopped it with 150 million ints because I didn't have the memory for 200 million and it sorted 150M in 49+ seconds. The built-in sort was consistently more than 1.5 times faster than my routine (29+ seconds for 150M). Obviously using the same method for sorting, but with better register control.
-
newton.saber wrote:
However, if you do something wrong (write a poor article) we are going to let you know.
Pretty standard behavior however. People are more likely to complain about anything than they are to compliment.
I've been ignoring you all, because you've all been making good comments. :-D
-
newton.saber wrote:
So, doing something wrong actually allows you to build more community (though it is constructed upon negativity) than doing something right. Ah, the human condition. It's a challenge
I tend to read the article and often ignore the comments. I figure most CP authors are savvy enough that they address the comments that have been made in the article long before I get there. I come here to learn from others that know more than I do. I figure an author has done their best on an article, so if misspelled words, poor grammar and non-compiling code is what their article contains, then that's probably the best they can do and there might not be much I can learn from them.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
patbob wrote:
I figure an author has done their best on an article, so if misspelled words, poor grammar and non-compiling code is what their article contains, then that's probably the best they can do and there might not be much I can learn from them
Well, I'll agree with you on the "non-compiling code" part, but a huge segment of the world comes from an area where English isn't the first language. I learned French as a second language in high school. I might attempt to read something written in French, but I wouldn't dare to write a word in it on a board. It takes a kind of courage to attempt something you know you aren't good at, that's something to admire. And what was written has the possibility to show me something I didn't know. I try to go beyond the grammer to see if they have something to teach me. As long as the article is technically competent, that's great, even if they don't teach me a thing. Sounds like this particular article would also have not taught me anything, so if I'd read it, I'd have to chalk it up as a waste of time. (A nitch which also holds the best written article when that article doesn't add anything to my knowledge.) I'd guess you could add this as an example of how not to write an article. :-D
-
To paraphrase my granny: If you can't say something nice, STFU". I'm not sure that there's a comparable saw in the US -- denigrating others seems to be more acceptable, there.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark_Wallace wrote:
To paraphrase my granny: If you can't say something nice, STFU".
I never saw any of my grandparents, but I did have a nephew three months before I was born. :-D You would have to paraphrase what you just said to get the common saw used in the US, but at least 50 years ago it was a common saw here in the states too. We yanks are taught to be rebellious, it's part of our heritage to be proud of. So, of course most kids don't listen to their parents. Then we get mad at them for following their heritage. We make total sense over here, right?