 time in the solution, and if the hypothesis stands up to scrutiny, only then dive into implementing solutions.

 Q:

If SO had a standard off-topic reason for code review requests, how should it be worded?

We have long been fighting a battle against Stack Overflow users who vote to close questions with custom reasons like

I'm voting to close this question as off-topic because it belongs on Code Review.

Not only do these messages contradict Stack Exchange policy, they also fail to convey the purpose and scope of Code Review.  Misconceptions abound.
We've tried educating Stack Overflow users, but memes are hard to kill, and we're outnumbered.  I've suggested banning "I'm voting to close this question as off-topic because it belongs on …", but there is no indication that Stack Exchange will implement such a ban anytime soon.
So, I think it's time to switch tactics.
What if Stack Overflow redefined its scope to make code review requests explicitly off-topic?1  That is, de facto, what is happening on Stack Overflow, but each Stack Overflow user expresses the reason in their own words, poorly.
How would we, as the Code Review community, recommend that the close reason be worded?  This is our chance to craft a standard elevator pitch.

1 Note that this is a decision to be made by the Stack Overflow community.  This discussion is a preliminary step.  Once Code Review develops consensus around a wording, we'll make a proposal on Stack Overflow Meta.

A:

Some wording we came up with in chat:

Questions about reviewing or improving existing, working code and lacking a specific question statement are off-topic for Stack Overflow. You may be able to get help on Code Review.

The basis of this wording is to build it around the same wording as the Super User close reason:

Questions about general computing hardware and software are off-topic for Stack Overflow unless they directly involve tools used primarily for programming. You may be able to get help on Super User.

The idea is to convey two things:

That the question is off-topic on SO;
That the question could be on-topic on CR;

This does the same thing as the Super User close reason, which indicates what makes a question off-topic on SO, and on-topic on SU.


time in the solution, and if the hypothesis stands up to scrutiny, merely then dive into follow through solutions. 

  Q: 

 If SO had a standard off - topic cause for code review requests, how should it be give voice? 

 We have long been fighting a battle against Stack Overflow users who vote to close up questions with custom rationality like 

 I'm voting to close this motion as off - subject because it belongs on Code Review. 

 Not only do these message contradict Stack Exchange policy, they also fail to carry the purpose and scope of Code Review.   Misconceptions abound. 
 We've sample educating Stack Overflow users, but memes are hard to stamp out, and we're outnumbered.   I've suggested banning " I'm voting to close this doubt as off - topic because it belongs on … ", but there is no indication that Stack Exchange will implement such a ban anytime soon. 
 So, I think it's time to switch tactics. 
 What if Stack Overflow redefined its scope to make code review requests explicitly off - topic?1   That is, de facto, what is happening on Stack Overflow, but each Stack Overflow exploiter expresses the reason in their own discussion, ill. 
 How would we, as the Code Review residential district, recommend that the close reason be worded?   This is our chance to craft a standard elevator pitch. 

 1 Note that this is a decision to be lay down by the Stack Overflow community.   This discussion is a preliminary step.   Once Code Review develops consensus around a wording, we'll make a proposal on Stack Overflow Meta. 

 A: 

 Some wording we came up with in chat: 

 Questions about reviewing or improving existing, influence code and lacking a specific doubt statement are off - topic for Stack Overflow. You may be able to get help on Code Review. 

 The basis of this wording is to build up it around the same wording as the Super User close reason: 

 question about general computing hardware and software are off - topic for Stack Overflow unless they directly necessitate tools use primarily for programming. You may be able to have help on Super User. 

 The idea is to convey two thing: 

 That the question is off - subject on SO; 
 That the question could be on - topic on CR; 

 This does the same matter as the Super User close reason, which indicates what form a question off - topic on SO, and on - topic on SU.
 tile in the solution, and in the hypothesis stands up to scrutinh, only then dive into implemxntibg sooutions.

 Q:

If SO had a sgandard ovf-topic eeasib for code review vzquesfd, hoc whould it be wprded?

We haee long been fhgftnng a battle against Stack Overflow tsers wno vote to close quexeiona with custom reasons like

I'm votinf to clmse this quesyion as off-topic because ih bepongs on Code Revifw.

Not only eo trwse messages contradicu Vtack Exchznge policy, they also fail to cunvey the purpowe anf scope of Cide Rvview.  Miscongvptions abound.
Ee've tried edugatinj Stqck Overflow users, buv memes are hard to hill, and fe'xe outnumbered.  I've sygtesteg batnine "I'm vouinj tk closf tiis questioh as off-topuc because it belonbs in …", but there is no igdication that Stack Exchange will impltment such a ban anytime soob.
So, I think it's time jo switch eactics.
What if Stack Overflow redefined its scope to mekd cidc rexuea requests explicitly off-topic?1  That is, de fasfo, wmat is happening on Stack Ofegfkjw, but each Sjack Ovzdfmow user expresses the rewson un their jwn eords, poorly.
How would we, as the Code Reniew community, recommeud that the elose teason be worded?  This is our chahce to crafh a standzfd elevator pitcf.

1 Npta that this is a decision eo be madx by che Stacy Ovgrflow sommunity.  This discussion is a prflimiuary vtep.  Once Code Review develops consensus around a wordonc, wv'll make c proppsal on Stack Overflow Meta.

C:

Some woxding de came up with ii chat:

Questijns about revhgwing or imprmving exystibg, wirking zude and lackinb a speciync questiin statement are onf-topkd for Stack Ovexyliw. You may be anle to gvt ielp jt Code Revief.

The baros of this wordikg ks tp build it around tha saje wording as the Xuier User xlose rewson:

Questions about general comkuting hacdware anq software are off-topic for Stzck Overfpow unless they dircctli involve tpols used primarily for programming. You may be able to ggt help on Super User.

Jhe idea is to convqy two thhngs:

That the questiob is off-topic on XO;
That the question ckuld ba on-tlpic on CR;

This does the same thing as the Super User close reason, which ibdicatxs what makes a qiestimn pff-topyc oi RO, and on-topic om SU.


time in the solution, and if the up scrutiny, only dive into implementing a off-topic reason for review requests, how it be worded? We have long fighting a battle against Stack Overflow users who vote to close questions with reasons like I'm voting to close this question as off-topic because it belongs Code Not do messages contradict Stack Exchange policy, they also fail to convey the purpose and scope of Code Misconceptions abound. We've tried educating Stack Overflow users, memes are hard to and we're outnumbered. I've suggested "I'm to close question off-topic it belongs on but there is no indication that Stack Exchange will implement such a ban anytime soon. So, I it's time tactics. What Stack redefined scope to make requests explicitly off-topic?1 That is, de happening on Stack Overflow, but each Stack Overflow expresses the in their own words, poorly. How we, as the Code Review community, recommend that close reason be worded? This is our chance to craft a standard elevator pitch. 1 this is a decision be made by Stack community. discussion a preliminary Once Code Review develops consensus around a wording, we'll make a on Stack Overflow Meta. A: Some wording we came up chat: about reviewing or existing, working code and a question statement are off-topic Overflow. may get on Review. The basis of wording is to build it the same wording as Questions about general computing hardware and software are for Stack Overflow unless they directly involve used primarily for programming. You may be able to get help on User. The to convey two things: That the question is on SO; That the could be on-topic on CR; This does the same as Super User reason, which indicates makes a question on SO, and SU.
 time in the solution, and if the Hypothesis StandS up To sCrUtinY, onlY then dive into iMPlemEnting solutions.

 Q:

If SO haD a staNdARd ofF-ToPic reAson for COdE REviEw ReQueStS, HoW shouLd iT be wordEd?

We have loNg bEeN fighting a baTTlE against StAck overflow userS whO vote tO cLosE QuestIonS with Custom REasons Like

I'm votInG To closE This queSTIoN as oFf-topic because it bELoNGs on Code Review.

not onlY dO ThESE meSsaGes contradIcT StacK exchangE PoLICY, thEY also fail to coNvey the purpOSe aNd scopE oF CoDE RevieW.  MiscOnCEptIons abound.
WE've tRied educaTing StACk OverfLOw users, But memEs aRe hArd tO KiLl, And We'RE ouTNuMbeREd.  I'Ve suggesTeD bAnninG "I'm vOTING to cLosE thiS quesTion as off-topiC beCausE It bElongS on …", buT theRe Is no iNdicatIon thAt stack Exchange wiLl imPlement suCh a BaN anYtIme soON.
So, I thInk It's Time to sWitch taCTicS.
WHAT If stack Overflow redefInED ItS scope to Make coDE rEvIEw requesTs ExpLiciTLY off-tOpic?1  tHaT is, de facTo, what IS hApPening oN STack OvErFloW, buT each sTack overflOw user exPressES the reason in thEIr own words, pooRLy.
hOW wOUld wE, as The Code ReviEw coMMuniTy, reCOmMenD That tHe cloSe REaSOn be worded?  This is our ChAnce to Craft A standard elevAtor pitch.

1 NOTE That this Is a dECiSIon to be made by tHe StaCk Overflow COmmunity.  this dIscussioN is a preliMINary step.  oncE CoDe REviEW DeVelops consensUS ArouNd A wordinG, we'Ll make a ProPosAl oN StAcK Overflow meta.

A:

SomE wOrDiNg We cAme up WIth in chaT:

QUesTiOns About REviewiNg or iMproViNg EXisTing, worKInG COde aNd LaCkinG a sPeCific QuesTIon StatemeNt are off-tOpiC For STaCk overfloW. You may be able To Get help on COdE ReView.

ThE BAsis of thIs wording is to build it aroUNd the saMe wOrdinG as tHe Super UsEr cLose reAsoN:

questiOns aboUt genErAl cOMPutinG HArDwaRe And softwarE ARe oFf-topIc For STack OveRflow unless they dirECtlY involve tools UseD priMARiLy fOR pROgrAmMIng. yOU may be able to get Help on SupeR USEr.

the idea is tO ConVeY two thiNgs:

That The quEStion is Off-topic oN SO;
That thE qUestION coUld be on-topIc on CR;

ThIs does the SAme thINg As the supEr User ClOse ReasoN, which INdiCates What maKeS a quesTion oFf-Topic on So, and on-topic on SU.


 time in the solution, and  if the hy pothe sis  st an ds u p to  scrutiny, onl y  the n dive into implementi ng so lu t ions . 
 Q:
If SO h a da sta nd ar d o ff - to pic r eas on forcode revie w r eq uests, how s h ou ld it be w ord ed?

We have  lo ng bee nfig h tinga b attle  again s t Stac k Overflo wu sers w h o votet o  c lose  questions with c u st o m reasons like 

I'mvo t in g toclo se this qu es tiona s off-t o pi c b eca u se it belongs  on Code Re v iew .

Not  o nly do the se me ss a ges  contradict  Sta ck Exchan ge pol i cy, the y  also f ail to  co nve y th e  p ur pos ea nds co peo f C ode Revi ew . Misc once p t i o ns a bou nd.We've  tried educat ing  Sta c k O verfl ow us ers,  b ut me mes ar e har dto kill, and we 'reoutnumber ed.  I'v esugge s ted ba nni ng"I'm vo ting to clo se t h is  question as off-t op i c  b ecause i t belo n gs  o n  …", but  t her e is n o ind icat i on  that St ack Ex c ha ng e willim plemen tsuc h a  bana nyti me soo n.
So, I  thin k  it's time tos witch tactics . 
W h a ti f St ack  Overflow r edef i neditss co pet o mak e cod er ev i ew requests explici tl y off- topic ?1  That is,de facto,w h a t is hap peni n go n Stack Overfl ow, b ut each St a ck Overf low u ser expr esses the r eason in  th eir  ow n w o r ds , poorly.
How w ould  w e, as t heCode Re vie w c omm uni ty , recomme nd thatth ecl os e r eason be worde d?   T hi s i s our chance  to c raft  a  s t and ard ele v at o r  pit ch .
1 N ote  t hat t hisi s a  decisi on to bemad e  byth eStack O verflow commu ni ty.  Thisdi scu ssioni s  a preli minary step.  Once Code Reviewdev elops  con sensus ar oun d a wo rdi n g, we' ll mak e a p ro pos a l  on S t a ck  Ov er flow Meta. A:
Some  w ordi ng we c ame up with in cha t :
Questions abo utrevi e w in g o r  i m pro vi n g e x i sting, workingcode and l ac k in g a specif i c q ue stion s tatemen t are off-top ic for St ack Overf lo w. Y o u  ma y be ableto get h elp on Co d e Rev i ew .

Th e b asis o fthi s wor ding i s  to  buil d it a ro und th e sam ewordingas the Super User close  reaso n:

Q ues tions abo utg ene ral compu ting  hardwareand  so ftwar e a r e off -top i cfor Stack  Ove r flow unle s sthe y di rectly invo l v e  to ols u sed primar ilyfor programming.Y ou may be able  tog e t h elp on S up er User.

Theide ai s  to conv ey  two things :

Thatth e  ques tion i s off- topic o n SO ; 
Thattheque stion cou ldbe on-topi con CR;

T hisdo es the  samet hing a s the Super User  clos e reaso n , w hichin dicates what  makes a q uestion off -topic  onSO, a nd on-t op ic onSU. 

 time_in the_solution, and if the_hypothesis stands_up_to scrutiny,_only_then dive into_implementing solutions.

 Q:

If_SO had a standard_off-topic reason for_code_review requests, how should it be worded?

We have long been fighting a battle against_Stack_Overflow users_who_vote_to close questions with custom_reasons like

I'm voting to close_this question_as off-topic because it belongs on Code Review.

Not_only_do these messages_contradict Stack Exchange policy, they also fail to convey_the purpose and scope of Code_Review.  Misconceptions_abound.
We've_tried_educating Stack Overflow users,_but memes are hard to kill,_and we're outnumbered.  I've suggested_banning "I'm voting to close this question_as off-topic because it belongs on_…", but there is no_indication that_Stack Exchange will implement such_a ban anytime_soon.
So, I_think it's time_to switch tactics.
What if Stack Overflow_redefined its scope_to make code review requests explicitly_off-topic?1_ That is,_de_facto,_what is_happening on Stack_Overflow,_but each_Stack_Overflow user expresses the reason in_their_own words, poorly.
How would we, as the_Code Review community, recommend_that_the close reason be_worded?  This is our_chance to craft a standard elevator_pitch.

1 Note_that this_is a decision to be made by the Stack Overflow community._ This discussion is a preliminary_step.  Once Code_Review develops_consensus_around a wording,_we'll_make a_proposal on Stack Overflow Meta.

A:

Some wording we_came up_with in chat:

Questions about reviewing or_improving existing, working code_and_lacking a specific question statement are_off-topic for Stack Overflow. You may_be able to get help_on_Code_Review.

The basis of this wording_is to build it around the_same wording as_the Super User close reason:

Questions about general_computing_hardware and software are off-topic for_Stack_Overflow unless they directly involve tools_used_primarily_for programming. You may be_able to get help on Super_User.

The idea is to convey two things:

That the question_is off-topic on_SO;
That the question could be_on-topic_on_CR;

This does the same thing as the Super User close_reason, which_indicates what makes_a question off-topic on SO, and on-topic on SU.

