So I ran into a question where someone asked if we could give him feedback about his new PHP MVC framework. I couldn't decide whether to close it or not. On one hand, SO seems like a good place to ask something like that, but on the other, it's not really a "question", and doesn't have any correct answers. I ended up voting to close it as "Not a real question". Was that right? Should we allow such "give me feedback on my framework/application" questions?
This was asked a while back on SO itself concerning "code reviews" and it received positive feedback. I actually posted a Code Review question myself and it turned out well. I received some very good critiques and took that advice towards building a better DAL.
As long as there isn't a super massive chunk of code and the author of the post is pretty clear about what areas he is looking for critiques on, I don't see a problem with it.
Edit: Here is the actual topic I posted. Code Review: ADO.NET Data Access Utility Class (VB) (yes, there is what you might consider a super massive chunk of code in there).
Edit 2: If the author of the post doesn't make it look like he is putting any decent effort into his question (such as being clear about what he is looking for help on or what specific areas to look at), then it is unlikely to receive much feedback from the community except close votes. In the cases of pure author laziness, I would probably vote to close myself. But if it looks like someone actually put a concerted effort into getting some useful feedback from the community, try it out and see how you can help the author.
I think it depends on how abstract it is.
If they are describing their framework in a manner that is abstract and COULD be applied to other questions, but it isn't SO abstract as to be useless, then yes, we can offer guidance on their framework.
If it is so specific that they write out 500 lines of code, and ask us to look through it, then no, SO isn't the place for that.
I've rethought it, "Give Me Feedback" isn't really a StackOverflow relevant question because it doesn't reflect a well thought out question. If you can specify the single part, function, class or algorithm that you aren't sure of, the you are indicating that you have done your best. If you are simply saying "Here's what I did, what do you think?" then that is something that should be taken up internally in a code review. SO is for questions which can be broadly applicable, and although this person may make some common mistakes, they aren't going to come up in a
If the user says "I've created a framework X, and this part Y could have been implemented in three ways and I chose A, but I'm wondering if B or C could have been better, given my framework, what do you think??" That would be acceptable, because it shows that the person has attempted to highlight the specific area that they need guidance on, rather than a catch-all "do my review for me".
I could see spinning this out into its own site. I found http://cr.opensolaris.org/ but did not find other dedicated code-review sites.
In trying to learn F#, I'm wanting to find out if my short programs are idiomatic. But "short" is a relative term, and SO is not designed for uploading or reviewing source code (other than brief excerpts).