I'm sure the immediate answer is no. However, slowly but surely, I'm seeing more people, for the most part beginners, completing projects and posting their code for review. So, in the very likely case that we will not be having a code review forum, what would be the best way to go about having anyone post code that they want the community to review and comment on? Your thoughts? Personally, I don't know. That's why I'm asking.

Counter Question - If their code works, why would they post for review ? Normally, the post I see of code is because it does not work. When my code works, I am happy, and I press on. How about forming something to help young coders market their talents. Or a Testers group. A group formed to test compiled cose and give feedback ?

Counter Question - If their code works, why would they post for review ? Normally, the post I see of code is because it does not work. When my code works, I am happy, and I press on.

Umm.. because sometimes you want to know how you could improve your design and generally write more elegant code? Going at it with the mindset that "if it compiles, it works" is a surefire way to get yourself in a productivity black hole once your code becomes impossible to maintain (and too expensive to refactor) as a result of brainless code-monkeying.

Code review does not mean "this does not work, fix it", it means "so I've done this, but this method here looks kind of awkward, how can I improve my interface to expose the minimum functionality possible while keeping it flexible, I need to query the database twice here, how could I refactor to require only one lookup, etc..", that kind of stuff.

If their code works, why would they post for review ? Normally, the post I see of code is because it does not work. When my code works, I am happy, and I press on.

How would the other forums be moderated? Does it mean any topic that is started with source code in it must be moved to the code review forum? That could be a pain to moderate... unless it is made very clear, especially for new members.

I think it'd be a diffrence between if the poster is indicating they want their code to be checked over, or are just having a problem.

Personally, I can't say i've seen a decent volume of code review request posts that it warrants it's own forum yet. But that's just me.

It's not like the requests are overflowing, however there has been a steady uptick in them lately. Plus, as developers I would think we would want a place to post code for review, if we wanted it. The question, that I have, is what's the best way to go about it. Should we have groundrules, templates, certain tags (as examples)? Should there be a forum? Should we just tell other users to post elsewhere and post a link here?

Counter Question - If their code works, why would they post for review ? Normally, the post I see of code is because it does not work. When my code works, I am happy, and I press on.

You need to define what you mean by "works"? Does it compile clean? Are there subtle bugs? Does it run fast? Does it integrate well? Is it maintainable? Is it even readable? Todays working code can quite easily become an absolute nightmare in 6 months time, and one of the reasons for reviewing code is to help prevent that from happening.