How to NOT write a zombie.
A zombie is a question that remains unanswered. As a question asker, your goal is to avoid writing one.
Beyond meeting the on-topic requirements, I think "good CR questions" can be broken down into several question types.
This answer is longer than I would have liked, but there are pictures.
These questions show ...
Simon's Guide for posting a good question
There are a lot of questions that appear on Code Review, and all questions are fighting for reviewer attention. This is a non-exhaustive list of items that I am looking for in a Code Review question when determining whether or not I should review it and how I should vote on it.
If your question is lacking a lot of ...
I have one problem with this. Assuming that there was a blog that we can contribute to, would there be contributions?
It's nothing against the people here, trust me.
If we look at all the blogs and see how many posts have been made since 1st jan 2014:
Science Fiction & Fantasy: 54
Server Fault: 7
Super User: 2
Information Security: 9
Good code doesn't mean nothing can come out of a peer review.
Reviewing code doesn't always mean shred the OP's code to pieces, and propose better ways to do the same thing. It could just as well point out why every right decision was the right decision to make.
I don't have an example at hand, but if Eric Lippert were to post some piece of the C# compiler ...
Enough! Enough! If you post any more answers here, we're going to run out of room in the database!
Er, I mean, you've done a good job of presenting evidence, and have convinced us on the Community Team. As of about ten minutes ago, MathJax has been enabled for Code Review. Use it well!
Tags for specific community-owned projects are nice, and rubberduck has been a good tag.
However, this does not mean that anyone and everyone can/should say "I'm gonna post all my code for project XYZ so I'm gonna tag my first question that I will post right now with the XYZ-tag".
It is preferred if the questions come first and the tag later.
There are ...
StackOverflow is an amazing resource for getting answers when you're stumped on a specific problem in your code and everything you've tried still doesn't make it work, and Google isn't helping you either.
Posting working code on StackOverflow is likely off-topic, because there's no problem to solve.
So you've posted your specific issue on SO, got some ...
Code Review should have a blog.
The benefits I see are:
a mechanism for less fact-based / more opinion based content that the Q&A component
another way to allow the community to participate and express themselves... perhaps:
no formal 'bloggers' per se
'committee' of some sort that 'vettes' submissions.
A place to describe the culture of Code ...
It seemed like a good idea at the time (Prompt for more meaningful question titles). However, it seems like either
People have a hard time trying to satisfy both requirements, and/or
Some people just won't read instructions no matter what.
I propose that we try a new prompt:
State the task that your code accomplishes. Make your title distinctive.
Code Review with a blog is a very good idea.
Although many codes are posted here for review, I think the common points can be accumulated and as a learning be shared in the blog along with some code snippets.
This can help in analysis, and will also invite people who would not come to CodeReview post because they were not concerned with the code under ...
The best thing to do is to read the Help Center, and specifically, in your case, where your questions are not off-topic, but not that well received:
How do I ask a good question?
That said, Meta is not meant to check if a question is OK before asking it, usually. The guidelines are pretty clear, and generally downvotes are used by members to indicate it is ...
200+ rep on other sites will give you the 100 rep bonus which is enough to do the regular things like comment and up-vote.
As for tagging, I would argue that tags are not strictly transferable and what makes a good tag on one site will not always make a good tag on another site. To that end I think its good that users need to spend some time on a site ...
I personally quite like that "warning", it inspires you to create titles that are more imaginative than "FizzBuzz from a file" - how about "IFSFB - Input File Specified FizzBuzz"
Do something different, something that will stand out.
The alternative will be thousands of questions called: "Singly Linked List", or "FizzBuzz", or "Project Euler #13"
If we ...
This site being Code Review, we require working code. We review excerpts of code that aren't complete programs. They could be library functions or even just a line or two of code.
Let's not change our wording from "code" to "program" just because some users have an excessively liberal concept of what "working" means.
I think if it's possible, we definitely should. Unlike other stack exchange sites the posts made here aren't really questions, at least not by the primary definition of the term. Which I agree is somewhat misleading.
Although posts may contain a question, more often than not when the main objective is asking a question, it's off-topic. I personally use ...
Scrolling up and down between the OP and the answer-in-progress is utterly wasteful and annoying.
A work-around I've come to use whenever possible, is to duplicate the browser tab, drag it to a 2nd monitor and work with the OP on one side and my answer-in-progress on the other.
It would be nice to be able to toggle a display mode that splits the page in ...
On Server Fault, for example, new users see a click-through warning when asking any question.
Considering that Code Review puts 30% of its questions on hold (though many questions are eventually reopened), it may be time to consider adding this minor obstacle.
Based on Space Exploration SE's similar feature request, the SE devs would want to see a list of questions that can benefit from this feature. We may not use this feature a whole lot, but we at least need several good examples of posts that would benefit from this. Even then, they may not feel that it's a good fit for CR, but that's something they will ...
I think you are thinking of the iterative process for an entire production size application, that is not what we do on Code Review.
If the process goes farther than like 10 iterations, it's a very large piece of code, and we would have told the user the first post that they need to break it up into several questions, or start with smaller pieces.
17 questions is substantial, it is also active, and growing.
There are a number of people who would 'follow' or favourite the tag.
The tag would describe the context in which the code is being developed, and would provide significant information value to anyone inspecting the questions
For the above reasons, I believe the tag would be useful, and should ...
Wait a bit longer.
11 days is not enough time to start evaluating a long-term experiment. Wait 2 more weeks and let's see if we have more cases at that time.
It could be a fluke, after all the newest of new users may not even realize what post comments are for, or how chat works, let alone the intricacies of what is on or off-topic on Code Review.
You can do this using bounties.
Get an answer you want to reward. Take this one (this is the question I got the images below on).
Select the 'start a bounty' option.
Select the size of the bounty you want.
Select the 'reward existing answer' option.
Yeah, this probably should've been done long before now - it's clear this has become a persistent problem here.
Starting now, the following words/phrases are not allowed in titles:
"question" (unless followed by "mark")
any sentence starting or ending with "help" or "problem"
I can't do much about the mess that'...
The following sites support MathJax (there may be more I'm unaware of):
Theoretical Computer Science
If even Biology supports MathJax, then leaving MathJax disabled on Code Review looks more like an oversight ...
NO - the limit should not be increased.
As it is, many answered questions have no accepted answers.
By making a question asker have to check-back again to accept an answer is likely to lead to even fewer questions with accepted answers.
Something like this could work:
Your question must contain your own real, working code.
Your question should provide an explanation of the code.
Your question may include a list of specific concerns.
This should be obvious to anyone who has read and understood the material in the relevant parts of the help center, though.
Creating a "reader's ...
The answer to the first part of your question I think should be: As many as you need.
However.... be reasonable. You can't ask a follow-up to an unanswered question. You shouldn't ask a follow-up to a question you haven't marked an accepted answer to. And the code in your follow-up question should address every point in the answers provided or explain ...
Stack Exchange is a network of question-and-answer sites. Code Review is one, too — it says so on our tour page.
Should we rename the "Ask Question" link? I don't think so, at least not as a reaction to one very confused user among the thousands of happy customers. Anything else would be inconsistent, not as succinct, and could make things worse. For ...