To Indian Article Posters
-
I'm not saying this because I think *all* Indians are terrible at posting articles, but the majority of poorly written articles are, in fact, posted by Indians (or at least this has been the case since the moderation process has been put in place). I know, some of you are going to say I'm wasting my time posting this, but if I don't say what I'm thinking, I tend to get testy, acidic, and/or downright mean. With that out of the way, on with the show. 0) Please find someone that speaks fairly good English to help you with your article. I'm not at all interested in reading an article that includes a high number of punctuation errors, transposed words, incorrect words, and any number of other syntactic errors. I realize English is a difficult language to master, but this is an "English spoken here" website, and you would do well to conform to that standard. 1) Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article. 2) Take the time to PREVIEW your article before submitting it. There's a Preview button there, and it takes just a minute or so to verify that your article looks right. 3) When you resize your images to fit within CodeProject limits, VERIFY that the image is still readable. 4) Do NOT re-submit your article if it doesn't immediately appear in the list of articles. There's a moderation process that all articles (posted by bronze/silver members) must go through before they are made available for consumption by the general CodeProject population. 5) Unless your article is relatively long, do not post links to other web sites where "a complete explanation is provided". I really do want to approve more articles than I do, but y'all are making it impossible for me to do. For all you VB programmers out there that are confused by my item numbering scheme, real languages (like C/C++) index lists and arrays starting at 0, so I figured I would extend that tradition to textual lists as well.
"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'm not saying this because I think *all* Indians are terrible at posting articles, but the majority of poorly written articles are, in fact, posted by Indians (or at least this has been the case since the moderation process has been put in place). I know, some of you are going to say I'm wasting my time posting this, but if I don't say what I'm thinking, I tend to get testy, acidic, and/or downright mean. With that out of the way, on with the show. 0) Please find someone that speaks fairly good English to help you with your article. I'm not at all interested in reading an article that includes a high number of punctuation errors, transposed words, incorrect words, and any number of other syntactic errors. I realize English is a difficult language to master, but this is an "English spoken here" website, and you would do well to conform to that standard. 1) Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article. 2) Take the time to PREVIEW your article before submitting it. There's a Preview button there, and it takes just a minute or so to verify that your article looks right. 3) When you resize your images to fit within CodeProject limits, VERIFY that the image is still readable. 4) Do NOT re-submit your article if it doesn't immediately appear in the list of articles. There's a moderation process that all articles (posted by bronze/silver members) must go through before they are made available for consumption by the general CodeProject population. 5) Unless your article is relatively long, do not post links to other web sites where "a complete explanation is provided". I really do want to approve more articles than I do, but y'all are making it impossible for me to do. For all you VB programmers out there that are confused by my item numbering scheme, real languages (like C/C++) index lists and arrays starting at 0, so I figured I would extend that tradition to textual lists as well.
"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/2001That is a good summary of what article writers need to do.
Recent blog posts: * Introduction to LINQ to XML (Part 1) - (Part 2) - (part 3) My website | Blog
-
I'm not saying this because I think *all* Indians are terrible at posting articles, but the majority of poorly written articles are, in fact, posted by Indians (or at least this has been the case since the moderation process has been put in place). I know, some of you are going to say I'm wasting my time posting this, but if I don't say what I'm thinking, I tend to get testy, acidic, and/or downright mean. With that out of the way, on with the show. 0) Please find someone that speaks fairly good English to help you with your article. I'm not at all interested in reading an article that includes a high number of punctuation errors, transposed words, incorrect words, and any number of other syntactic errors. I realize English is a difficult language to master, but this is an "English spoken here" website, and you would do well to conform to that standard. 1) Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article. 2) Take the time to PREVIEW your article before submitting it. There's a Preview button there, and it takes just a minute or so to verify that your article looks right. 3) When you resize your images to fit within CodeProject limits, VERIFY that the image is still readable. 4) Do NOT re-submit your article if it doesn't immediately appear in the list of articles. There's a moderation process that all articles (posted by bronze/silver members) must go through before they are made available for consumption by the general CodeProject population. 5) Unless your article is relatively long, do not post links to other web sites where "a complete explanation is provided". I really do want to approve more articles than I do, but y'all are making it impossible for me to do. For all you VB programmers out there that are confused by my item numbering scheme, real languages (like C/C++) index lists and arrays starting at 0, so I figured I would extend that tradition to textual lists as well.
"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/2001Maybe most of "bad" articles are from Indian people, but I think you should rename it to "all article posters", and even ask Chris to add it to the beginning of the article submit info page[^], they are actually good hits for all. 5 for that. EDIT: Correction in bold
Greetings. -------- M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you “The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson Rating helpfull answers is nice, but saying thanks can be even nicer.
modified on Thursday, May 29, 2008 10:59 AM
-
Maybe most of "bad" articles are from Indian people, but I think you should rename it to "all article posters", and even ask Chris to add it to the beginning of the article submit info page[^], they are actually good hits for all. 5 for that. EDIT: Correction in bold
Greetings. -------- M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you “The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson Rating helpfull answers is nice, but saying thanks can be even nicer.
modified on Thursday, May 29, 2008 10:59 AM
Why should I mention others when 95 out of 100 articles I report are from Indians?
"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'm not saying this because I think *all* Indians are terrible at posting articles, but the majority of poorly written articles are, in fact, posted by Indians (or at least this has been the case since the moderation process has been put in place). I know, some of you are going to say I'm wasting my time posting this, but if I don't say what I'm thinking, I tend to get testy, acidic, and/or downright mean. With that out of the way, on with the show. 0) Please find someone that speaks fairly good English to help you with your article. I'm not at all interested in reading an article that includes a high number of punctuation errors, transposed words, incorrect words, and any number of other syntactic errors. I realize English is a difficult language to master, but this is an "English spoken here" website, and you would do well to conform to that standard. 1) Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article. 2) Take the time to PREVIEW your article before submitting it. There's a Preview button there, and it takes just a minute or so to verify that your article looks right. 3) When you resize your images to fit within CodeProject limits, VERIFY that the image is still readable. 4) Do NOT re-submit your article if it doesn't immediately appear in the list of articles. There's a moderation process that all articles (posted by bronze/silver members) must go through before they are made available for consumption by the general CodeProject population. 5) Unless your article is relatively long, do not post links to other web sites where "a complete explanation is provided". I really do want to approve more articles than I do, but y'all are making it impossible for me to do. For all you VB programmers out there that are confused by my item numbering scheme, real languages (like C/C++) index lists and arrays starting at 0, so I figured I would extend that tradition to textual lists as well.
"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/2001John Simmons / outlaw programmer wrote:
if I don't say what I'm thinking, I tend to get testy, acidic, and/or downright mean.
If you don't say? :-D 5'ed, anyway.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Photos/CP Flickr Group - ScrewTurn Wiki
-
Why should I mention others when 95 out of 100 articles I report are from Indians?
"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/2001What a way to accept a compliment :doh: :( I know that you are reporting indian articles, but I find your tips good for everyone. But you live in a free country, do whatever you want. :| EDIT: Correction in bold
Greetings. -------- M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you “The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson Rating helpfull answers is nice, but saying thanks can be even nicer.
modified on Thursday, May 29, 2008 9:39 AM
-
I'm not saying this because I think *all* Indians are terrible at posting articles, but the majority of poorly written articles are, in fact, posted by Indians (or at least this has been the case since the moderation process has been put in place). I know, some of you are going to say I'm wasting my time posting this, but if I don't say what I'm thinking, I tend to get testy, acidic, and/or downright mean. With that out of the way, on with the show. 0) Please find someone that speaks fairly good English to help you with your article. I'm not at all interested in reading an article that includes a high number of punctuation errors, transposed words, incorrect words, and any number of other syntactic errors. I realize English is a difficult language to master, but this is an "English spoken here" website, and you would do well to conform to that standard. 1) Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article. 2) Take the time to PREVIEW your article before submitting it. There's a Preview button there, and it takes just a minute or so to verify that your article looks right. 3) When you resize your images to fit within CodeProject limits, VERIFY that the image is still readable. 4) Do NOT re-submit your article if it doesn't immediately appear in the list of articles. There's a moderation process that all articles (posted by bronze/silver members) must go through before they are made available for consumption by the general CodeProject population. 5) Unless your article is relatively long, do not post links to other web sites where "a complete explanation is provided". I really do want to approve more articles than I do, but y'all are making it impossible for me to do. For all you VB programmers out there that are confused by my item numbering scheme, real languages (like C/C++) index lists and arrays starting at 0, so I figured I would extend that tradition to textual lists as well.
"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/2001John Simmons / outlaw programmer wrote:
- Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article.
I second that. My biggest peeve with articles ever is finding one as a search hit, expecting to actually read some written word, and just getting a download link really pisses me off.
Semicolons: The number one seller of ostomy bags world wide. - dan neely
-
What a way to accept a compliment :doh: :( I know that you are reporting indian articles, but I find your tips good for everyone. But you live in a free country, do whatever you want. :| EDIT: Correction in bold
Greetings. -------- M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you “The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson Rating helpfull answers is nice, but saying thanks can be even nicer.
modified on Thursday, May 29, 2008 9:39 AM
Nelek wrote:
tipps
I know I'm pedantic but anyway, it's tips.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Photos/CP Flickr Group - ScrewTurn Wiki
-
I'm not saying this because I think *all* Indians are terrible at posting articles, but the majority of poorly written articles are, in fact, posted by Indians (or at least this has been the case since the moderation process has been put in place). I know, some of you are going to say I'm wasting my time posting this, but if I don't say what I'm thinking, I tend to get testy, acidic, and/or downright mean. With that out of the way, on with the show. 0) Please find someone that speaks fairly good English to help you with your article. I'm not at all interested in reading an article that includes a high number of punctuation errors, transposed words, incorrect words, and any number of other syntactic errors. I realize English is a difficult language to master, but this is an "English spoken here" website, and you would do well to conform to that standard. 1) Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article. 2) Take the time to PREVIEW your article before submitting it. There's a Preview button there, and it takes just a minute or so to verify that your article looks right. 3) When you resize your images to fit within CodeProject limits, VERIFY that the image is still readable. 4) Do NOT re-submit your article if it doesn't immediately appear in the list of articles. There's a moderation process that all articles (posted by bronze/silver members) must go through before they are made available for consumption by the general CodeProject population. 5) Unless your article is relatively long, do not post links to other web sites where "a complete explanation is provided". I really do want to approve more articles than I do, but y'all are making it impossible for me to do. For all you VB programmers out there that are confused by my item numbering scheme, real languages (like C/C++) index lists and arrays starting at 0, so I figured I would extend that tradition to textual lists as well.
"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/2001Thank you, John for consolidating a quick checklist for beginners aspiring to have their content published onto a premier technology website. I would suggest, if these points are also updated/included as part of the Article Publishing Guidelines that Pete has prepared (http://www.codeproject.com/KB/scrapbook/ForumGuidelines.aspx[^]), it would be reaching instead of as a forum post. The forum post might run off fast into the wild right? I admit that it is highly disgusting, nauseating and irritating see a broken language. People should learn the habit of using and referring dictionaries and cultivate an affection/love for it.
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
John Simmons / outlaw programmer wrote:
- Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article.
I second that. My biggest peeve with articles ever is finding one as a search hit, expecting to actually read some written word, and just getting a download link really pisses me off.
Semicolons: The number one seller of ostomy bags world wide. - dan neely
Brady Kelly wrote:
just getting a download link really pisses me off.
besides sending a chill down the spine for fear and outbreak of virus infections.
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
Nelek wrote:
tipps
I know I'm pedantic but anyway, it's tips.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Photos/CP Flickr Group - ScrewTurn Wiki
Thanks for the correction. I like it, I learn with it :)
Greetings. -------- M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you “The First Rule of Program Optimization: Don't do it. The Second Rule of Program Optimization (for experts only!): Don't do it yet.” - Michael A. Jackson Rating helpfull answers is nice, but saying thanks can be even nicer.
-
Brady Kelly wrote:
just getting a download link really pisses me off.
besides sending a chill down the spine for fear and outbreak of virus infections.
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis LevinsonVasudevan Deepak Kumar wrote:
besides sending a chill down the spine for fear and outbreak of virus infections.
:confused:
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
-
Thank you, John for consolidating a quick checklist for beginners aspiring to have their content published onto a premier technology website. I would suggest, if these points are also updated/included as part of the Article Publishing Guidelines that Pete has prepared (http://www.codeproject.com/KB/scrapbook/ForumGuidelines.aspx[^]), it would be reaching instead of as a forum post. The forum post might run off fast into the wild right? I admit that it is highly disgusting, nauseating and irritating see a broken language. People should learn the habit of using and referring dictionaries and cultivate an affection/love for it.
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis LevinsonI think the worst are the plagiarists: the others must realise they'll get rejected but these guys and gals ar ehoping to elicit credit for work that isn't theirs. That is the lowest of the low. Further, you are correct: when I see the list of new articles I'm expecting that if the author has an asian name the chances are the article is poor. My apologies, that just does not sound right no matter how I phrase it: I'm not intending to show bias or prejudice, just pointing out an oft observed phenomenon.
-
I'm not saying this because I think *all* Indians are terrible at posting articles, but the majority of poorly written articles are, in fact, posted by Indians (or at least this has been the case since the moderation process has been put in place). I know, some of you are going to say I'm wasting my time posting this, but if I don't say what I'm thinking, I tend to get testy, acidic, and/or downright mean. With that out of the way, on with the show. 0) Please find someone that speaks fairly good English to help you with your article. I'm not at all interested in reading an article that includes a high number of punctuation errors, transposed words, incorrect words, and any number of other syntactic errors. I realize English is a difficult language to master, but this is an "English spoken here" website, and you would do well to conform to that standard. 1) Write an actual article to go with your code. Simply posting downloadable source code and having a few lines of text supporting poorly formatted code blocks is NOT an article. 2) Take the time to PREVIEW your article before submitting it. There's a Preview button there, and it takes just a minute or so to verify that your article looks right. 3) When you resize your images to fit within CodeProject limits, VERIFY that the image is still readable. 4) Do NOT re-submit your article if it doesn't immediately appear in the list of articles. There's a moderation process that all articles (posted by bronze/silver members) must go through before they are made available for consumption by the general CodeProject population. 5) Unless your article is relatively long, do not post links to other web sites where "a complete explanation is provided". I really do want to approve more articles than I do, but y'all are making it impossible for me to do. For all you VB programmers out there that are confused by my item numbering scheme, real languages (like C/C++) index lists and arrays starting at 0, so I figured I would extend that tradition to textual lists as well.
"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/2001Actually, the problem is that those morons who submit half-assed articles won't have the brains to understand anything of what you said. This will remain as an ongoing process, irrespective of any number of discussions like this, any number of guidelines, write-ups teaching "how to do" something. This applies for the crap-posts in the technical forums as well. You just can't stop them. At least with the new moderation system, we can block out crap articles and I'm happy with that.
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
-
I think the worst are the plagiarists: the others must realise they'll get rejected but these guys and gals ar ehoping to elicit credit for work that isn't theirs. That is the lowest of the low. Further, you are correct: when I see the list of new articles I'm expecting that if the author has an asian name the chances are the article is poor. My apologies, that just does not sound right no matter how I phrase it: I'm not intending to show bias or prejudice, just pointing out an oft observed phenomenon.
digital man wrote:
I think the worst are the plagiarists: the others must realise they'll get rejected but these guys and gals ar ehoping to elicit credit for work that isn't theirs. That is the lowest of the low.
I really need a machine-gun to shoot them down ruthlessly or at least I need a gas chamber to squeeze those involving in 'Credit Theft' and gag them to death. I really hate people who take credit of others' and suck their blood and hardwork worser than a leech. I am voting a '5' for you since you added a significant ethical perspective to it.
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
Actually, the problem is that those morons who submit half-assed articles won't have the brains to understand anything of what you said. This will remain as an ongoing process, irrespective of any number of discussions like this, any number of guidelines, write-ups teaching "how to do" something. This applies for the crap-posts in the technical forums as well. You just can't stop them. At least with the new moderation system, we can block out crap articles and I'm happy with that.
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
Rajesh R Subramanian wrote:
those morons who submit half-assed articles won't have the brains to understand anything of what you said.
Translating to the Indian way, "they are just thick skinned buffaloes which give scant respect to the incessant honking of horns and they just cross the road nonchalantly."
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
Vasudevan Deepak Kumar wrote:
besides sending a chill down the spine for fear and outbreak of virus infections.
:confused:
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
http://idioms.thefreedictionary.com/send+chills+down%2Fup+spine[^]
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
Rajesh R Subramanian wrote:
those morons who submit half-assed articles won't have the brains to understand anything of what you said.
Translating to the Indian way, "they are just thick skinned buffaloes which give scant respect to the incessant honking of horns and they just cross the road nonchalantly."
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis LevinsonVasudevan Deepak Kumar wrote:
they are just thick skinned buffaloes which give scant respect to the incessant honking of horns and they just cross the road nonchalantly.
Looking at the posts you're making today, it makes me wonder if you're drunk. :~
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
-
Actually, the problem is that those morons who submit half-assed articles won't have the brains to understand anything of what you said. This will remain as an ongoing process, irrespective of any number of discussions like this, any number of guidelines, write-ups teaching "how to do" something. This applies for the crap-posts in the technical forums as well. You just can't stop them. At least with the new moderation system, we can block out crap articles and I'm happy with that.
Nobody can give you wiser advice than yourself. - Cicero .·´¯`·->Rajesh<-·´¯`·. Codeproject.com: Visual C++ MVP
I was trying to be nice, but yeah, you're right.
"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 -
That is a good summary of what article writers need to do.
Recent blog posts: * Introduction to LINQ to XML (Part 1) - (Part 2) - (part 3) My website | Blog
Truly useful; Timely pointers; Apt, Terse and Curt; :)
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson