5
\$\begingroup\$

I submitted this code yesterday, and I am just curious when it would be reviewed. I was looking forward to learning some new things.

\$\endgroup\$
  • 3
    \$\begingroup\$ You might want to read How can I make my question get more attention? \$\endgroup\$ – Simon Forsberg Jul 10 '17 at 16:50
  • \$\begingroup\$ ok, I will do that now \$\endgroup\$ – Ashton Morgan Jul 10 '17 at 16:51
  • 1
    \$\begingroup\$ The chat-active VBA crowd sees every single vba question asked on CR, SO and SU in the VBA Rubberducking chatroom. Reviewing code takes anywhere between 15 minutes and 3 hours or even more, depending on what's going on and how much there is to say about the code being presented (and how much effort reviewers are putting in anyway). Note that Stack Overflow is on a completely different pace; Code Review is much more relaxed; on SO you can get a two-liner answer in two minutes. Here you get a 2-pager answer in two hours, days, ...depends. \$\endgroup\$ – Mathieu Guindon Jul 10 '17 at 17:14
  • \$\begingroup\$ @Mat'sMug And how much time does it take to write an answer compared to a comment...? \$\endgroup\$ – Simon Forsberg Jul 10 '17 at 18:06
  • 1
    \$\begingroup\$ @SimonForsberg IDK... Everytime I try to keep it short and comment-fitting, I end up with a 2-pager answer... \$\endgroup\$ – Mathieu Guindon Jul 10 '17 at 18:14
9
\$\begingroup\$

Here is a Stack Exchange Data Explorer query, written by @LokiAstari and tweaked by me, showing the average time between the question and the first answer.

As you can see, there can be huge variations. Depending on how well you phrase the question and how complex the code is, you might get an answer within minutes, or it might never get answered. If it does get an answer, then a few days is a typical wait. (Currently, about 10% of all questions are unanswered, or have no upvoted answer.)

\$\endgroup\$

You must log in to answer this question.

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