This post is, partially, "inspired" by CHill's recent post here: "Up the number of reports to close a QA question?" ... but, I am starting a new thread because what I have to say is, I believe, on a different "level." I want to "frame" the issue of deleting QA posts by focusing on the broader context ... the thread as a whole including any comments, or posted solutions ... in which a given question appears.
This question exists in the context of the weird fact that deleted QA questions get stripped of their comments, and any posted solutions, yet continue to appear visible on the Forums: an absurdity resulting in wasted time for everyone: unless you consider reading "closed" notices fascinating That structural flaw is something only CP staff can address. In this post I choose to ignore the related phenomenon of rapid down-voting of new questions by certain very "dominant" participants in the QA forums.
When a QA question is:
0. accompanied by some included code (not a "code-dump") that indicates the OP is struggling with writing code themselves.
|| 1. quite "fresh" in time
|| 2. by someone relatively new to CodeProject, or someone whose use of English indicates they have great difficulty writing it.
|| 3. has had meaningful questions posted as comments on the OP which ask for clarification, etc.
|| 4. has had solution(s) ... particularly those that include working code ... posted by other CP members with good track-records (note: I do not assume that rep-points, or MVP status, have any linear relation to "good track record" here, since I consider the entire CP rep-system ... except for articles ... "structurally distorted, and frequently abused").
Then, I believe that closing the question before it has had some minimum "life-span" is a dis-service to CodeProject.
If other CP members who are obviously making a contribution to QA by posting working code, and thoughtful comments, take their time to post on a thread: closing it not only discards that content, but it also creates a dis-incentive for the person who is truly trying to be helpful on QA.
For example, when a question like this one: [^] ... posted, apparently in the later night-time in the US ... is closed within hours of its being posted, it's possible the OP has not even had a chance, during their daylight hours, to review the question, and its comments, and any posted solutions. On this question I asked several questions in a comment, and would have, likely, posted code, if the OP had answered.
I took the trouble to post a working code solution for this question [^], which I experienced as quite a clear question in the sense the OP showed at least some code.
The dangers of ignoring context are expressed clearly to me in statements like this one from RyanDev on the thread started by CHill below:
"Worst case scenario, the user asks the question again and hopefully adds some detail."
This completely ignores the fact that for many people, having a question removed may be experienced as a complete ... fill in the blank ... personal/intellectual rejection, breaking of face, insult, go-away-stay-away sign, etc. Note that those with their questions removed, to my knowledge, receive no notice of the question being closed, certainly no encouragement to post again.
I could go on further ... and farther ... but, if I haven't highlighted any issues that need to be addressed ... and which, if addressed, would result in a "better" CodeProject QA ... by this time, I'd say that what you have heard here is only burble.
« There is only one difference between a madman and me. The madman thinks he is sane. I know I am mad. » Salvador Dali
I just finished editing an article named "Start unit test code coverage by Jacoco" (or something like that if I do not remember correctly), but when I tried to submit it, I get an error on the web page, and I then lost the article.
I have tried to save the "Draft" all the time, now I do not even see the draft. I am not sure if you can help me to recover the draft.
Any help is appreciated, so I do not need to re-do the typing.
1. Yes, I did submit (with editing not to make public checked). But after clicking the submit button I then see an error page (the page shows a picture some bugs and some broken wires). I then clicked the back button on the web browser (I do not remember what the back button gave me, but it was something that was meaningless), when I refresh the page, I no longer see anything related to the article that I am working on.
2. I used the codeproject's submit wizard to edit the article. It tells me that the draft will be auto-saved. It does save automatic draft based on my previous experience, but not this time.
3. I do not remember if I have previously pending articles.
I know we get some absolute rubbish in there, but several seem to get closed down for no real good reason ... e.g. Path trough command?[^]
I worked out what he meant, clearly SA did too... although I never did get to see what he posted. Only 2 people quoted as deeming it unsuitable ... up to 5 maybe??
the list of reporters is another thing, if the reports get counted in different cathegories only the one with the biggest number of "votes" gets listed. I think the weight of the reporters (based on rep) has to do something as well, but not sure about it.
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.
Worst case scenario, the user asks the question again
The problem is that some won't: and they won't come back at all.
And quite a few questions seem to get closed purely because some members don't understand them - despite there being solutions, or a good conversation going to get the required info.
Asking questions is a skill: and to develop, it has to be used. Slam the door in the face of someone who hasn't developed it yet and that doesn't give them a chance to develop it at all...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
The question has got 3 reports, and 2 of the people who reported it chose "Unclear or Incomplete", and the third one chose another option, so that's why it just shows two people.
The number of reports used to be 5 but this was changed to 3 when we got a spam wave. We still get spam, but less spam than during that wave, and just 3 reports seems a bit few so I'd go for 4 reports.
The quick red ProgramFOX jumps right over the Lazy<Dog>.
It seems a bit low getting only 10 points for publishing a tip and trick. It will be better if we got lets say 25 points. It still requires enough work, not as much as an article, still more 10 for sure.
“The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser men so full of doubts.”
So. What are you going to do with the reputation points?
If you're aiming to be get a platinum rank it might be an easier and faster way to just publish good articles/tricks/tips instead of just lots of them. And the privileges for platinum authors should be for members that write good content. Quality over quantity.
Not meaning any offense, but: How does it matter then?
Considering the efforts: As far as I can tell a great article seems to be a lot more work than a Tip/Trick...
The other side of the coin is that many are now publishing something as an article which is a Tip at most.
You say, I should mind my business when it comes to writing? Well, I'm writing an opinion of when it comes to reading. The worth of a good article exceeds the worth of a good tip/trick by far. But that really depends on the article. And if the reputation points are something to encourage writing something I'd rather see more good articles instead of Tips/Tricks.
Last Visit: 31-Dec-99 18:00 Last Update: 25-Oct-14 0:36