3
\$\begingroup\$

I understand why a character limit is imposed on question lengths on most Stack Exchange websites, but I take issue with the fact that there is a 30,000 character limit on the Code Review website.

Surely the character limit for questions on the Code Review website should be raised due the fact that the difference between Stack Overflow and Code Review is for people to post much larger chunks of code or even whole projects for code review by peers?

\$\endgroup\$

migrated from meta.stackexchange.com Apr 23 '13 at 2:32

This question came from our discussion, support, and feature requests site for meta-discussion of the Stack Exchange family of Q&A websites.

  • 6
    \$\begingroup\$ I'll +1 this since it seems like a good idea, with the caveat that all posts on Code Review should highlight the areas of code that are being focused upon. Posts containing little more than 3000 lines of code are always bad. \$\endgroup\$ – Polynomial Apr 23 '13 at 0:27
  • 5
    \$\begingroup\$ On this site, good answers often need to be longer than the questions, so spare a thought for the answerers! (For example, here's an answer which I had trouble fitting into the 30,000 character limit.) \$\endgroup\$ – Gareth Rees Apr 23 '13 at 21:49
9
\$\begingroup\$

Thanks for your suggestion, but I have to disagree.

As is the nature of Code Reviews, each one of them is done on a case by case basis so we are already pushing the borders of Stack Exchange Q&A system (on other sites, most of our questions would be seen as too localized).

That said, I think of our site as a collection of useful case studies that others can learn from.
The about page puts it like this:

With your help, we're working together to build a library of detailed code reviews.

Once question length increases about a certain point, two problems stand in the way of this goal:

  1. Reviewers are put off because they don't have the time or energy to review vast walls of code. This contributes to our already below average answer ratio of 1.9

  2. The same thing happens for visitors only it's worse, because now they're facing a huge question and possibly several huge answers, which requires too much time and effort to learn anything from the whole endeavor.

Also keep in mind that good code reviews in real day-to-day scenarios are done at check-in. This implies that the code to review forms one logical unit (e.g. a feature or a class) and is not overly long.

Summary

Code Review should focus on providing concise case studies. These case studies should focus on a particular feature or class rather than entire projects (or large parts of them). Increasing the character limit is not helpful as it would worsen, rather than improve, the site.

\$\endgroup\$
6
\$\begingroup\$

Starting at some time in 2016 if I remember correctly, the character limit on Code Review is now 65535 characters.

\$\endgroup\$

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .