Recently I've been thinking about how to improve the quality of DZone, and here are some notes that I've made.
Disclaimer:I do not work for DZone.
Continue to post relevant stuff!
For everyone who is already contributing: You are the reason why I visit DZone. (The article you wrote two moths ago was great, you really managed to pinpoint the problem! That link you posted last week was interesting, I would never have found it if it didn't float to the top of DZone! Thank you for for taking time to moderate incoming links! ) If you find good articles or blog posts related to software or hardware development, please continue to post it.
Post good articles!
How can we define good articles? According to Dave Winer it is:
People talking about things they know about, not just expressing opinions about things they are not experts in (nothing wrong with that, of course).
Don't post links to links!
There's a saying that goes like this "copy one source and it is plagiarism, copy two or three sources and it is research."
If you want to post a link to DZone, make sure you either link directly to the source, or that you add significant value.
Don't post non-developer stuff
Remember, DZone is D(eveloper)Zone, not Digg, not Slashdot or any other general social networking/bookmarking site.
That means, if you find great stuff but it's not related to software or hardware development, please post it, but post it somewhere else. If somebody is interested in those articles too, they can visit digg, lifehacker and slashdot. I'm sure many DZone readers do already.
If you post a top n list, make sure it is a good one
Jurgen Appelo has described his preparations here: http://www.noop.nl/how-to-make-a-top-blog-list.html. Basically, if you think this is too much work, don't post the link.
Vote down
To quote the stackowerflow faq:
Be honest.
Above all, be honest. If you see misinformation, vote it down. Insert comments indicating what, specifically, is wrong.
Read before you respond
Sometimes articles are voted down because of what we, the readers, think the author is writing. As an example, the article When Windows beats Linux: a cautionary tale was downvoted eagerly and judging by the comments, the downvoters was most likely zealous Linux fans, who obviously had not read the article (It was pro Linux.)
Downvote this article
Now, this article is not related to software development, so you may just go ahead, follow my advice and downvote it, I don't care. Or, -if you think more people should be reading this, post it to dZone and vote it up.
Also, if you have any ideas about how to make a better DZone, please write it down in blog post, or if you are lazy, just make a comment.