|
|
.
Rules for the FOSW ![ ^]
if(!string.IsNullOrWhiteSpace(_signature))
{
MessageBox.Show("This is my signature: " + Environment.NewLine + _signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
|
.
Rules for the FOSW ![ ^]
if(!string.IsNullOrWhiteSpace(_signature))
{
MessageBox.Show("This is my signature: " + Environment.NewLine + _signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Most probably the wrong forum to ask this, but I don't like to make this in "too" public for the moment. Nevertheless...
Until now I do it like this for "re approving"
a.) Member has more than one publication here on CP -> +1
b.) Member is here for longer time -> +1
c.) Check article for links to paid or not serious sites -> +1
I do "Re Approve" in case if 3 Points 
Question: Is this ok or is this too negligent?
Btw. I don't believe that others go through the article sentence by sentence and are sure that everything fits 100%
Thank you in advance for your opinion/tip
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
If I can understand the subject matter, then I try to read the article. It becomes fairly clear early on if it is well or badly written, and I can approve or comment. If I do not (or can not) understand the subject I look for generally poorly written or formatted to see if it is worth commenting. If it looks well written then I leave it to people who understand the subject, unless the content is easy to read*. If it is obviously poor or spammy looking then I vote appropriately.
*I do not really understand the subject matter of FMBomb - A Beginner's Approach to Hardware Programming[^] but I think it is a classic example of how an article should be written. There are, of course, quite a few other authors whose articles are always excellent.
|
|
|
|
|
Thank you very much for this.
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
As Richard said...
If I can understand the topic. I do read it (but more due to curiosity than for the "approve" itself)
If I can't understand the topic. I just check about format, layout, some random sentences to check spelling and things like that. If everything is fine... then I sometimes approve it, mostly leave it for others who can understand the topic.
In other words... I click way more on "report format, spam, poor quality, etc" than on "approve"
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
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Thank you very much for this.
... Format, layout, spelling... I'm not sure whether this should the main criterias. Of course all these should fit, but never should be a criteria to Report negative.
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
0x01AA wrote: ... Format, layout, spelling... I'm not sure whether this should the main criterias.
These are exactly the criteria for the reports, see the options...
Reports that nuke the article:
Report says: Unclear / incomplete
extremly poor quality
spam
plagiarized
Innacurate / misleading
Reports that don't nuke the article and flag it for editors staff:
Needs Help says: Format / Layout
Wrong section / tags
Wrong type (blog, article, tip)
Missing images / donwloads
Images/downloads are offsite
0x01AA wrote: but never should be a criteria to Report negative.
Yes, they should.
As I said, even if I don't understand the technical contents. I still want the articles published to hold a standard.
If I see an article writen unprofessionally, with grammar errors that even I can see (non native english speaker), using "plz, codez or similars" (yes, I have seen several articles doing it), containing just a code dump without a comprehensive text explaining it, 3 sentences and 5 pictures reinventing the wheel, security flaws like SQL Injection in a login formular... Should I continue? I hope you get the point.
So I repeat: Yes, those are exactly the criteria for a "negative" report.
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
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Hmmm,
I've always been here for the code. The text in-between the code looks like Chinese to me. Some of the best 'Pulitzer-Prize' high quality articles on codeproject have crap code that any monkey could write.
Let me give an example that I've never forgot:
Many years ago Chris held a competition called "Lean and Mean"[^] and invited everyone to compete for the best diff algorithm. I was keenly interested and tested them all. The winners were announced[^].
Nobody ever knew it... but the best implementation was written as a comment by a random guy in the comment section[^].
Of course that guy didn't win. But it's absolutely the best code in the contest. It outperformed all of the others and passed all my tests. It's by far the best entry.
Codeproject is full of diamonds in the rough. Can you spot the diamonds?
Best Wishes,
-David Delaune
|
|
|
|
|
This seems reasonable
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
Randor wrote: Codeproject is full of diamonds in the rough. Can you spot the diamonds?
as I said:
Quote: then I sometimes approve it, mostly leave it for others who can understand the topic.
Randor wrote: Some of the best 'Pulitzer-Prize' high quality articles on codeproject have crap code that any monkey could write.
I see your point.
I can't show you my reports list, but if you could see it I am pretty confident, you wouldn't find many items to complain about my decision.
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
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
Spammer terminated.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
|
|
|
|
I can't say about the technical content. But the pictures are relative similar to the page that he links at the end of the article.
The link drives to a paid product with a free demo version.
I would say, let's summon @sean-ewington to have a look
In my opinion, the author might get a second chance, but the link should vanish.
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
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Bryian Tan
|
|
|
|
|
I have removed the article.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Thanks for showing up, Sean
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
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
