 what?  Will have to read the doc/code to know
<jimbaker`> niemeyer, sure, i can definitely make that change
<jimbaker`> in both names
<niemeyer> jimbaker`: E.g. watch_expose_flag is a good name for watch_service_changes
<jimbaker`> the first is to at least use our cb_ prefix to indicate callbacks
<niemeyer> jimbaker`: I'm ambivalent about it.. they are generally good hints when we can't figure something better that actuall describes the intention
<niemeyer> jimbaker`: Otherwise, twisted is all about callbacks.. we'll go crazy :)
<niemeyer> jimbaker`: Note that we generally use cb_<watcher function name>, if I remember correctly
<jimbaker`> niemeyer, certainly twisted is always about the callback, fortunately inlineCallbacks can make it more linear
<jimbaker`> but that's another line of thought
<niemeyer> jimbaker`: Which means we have the same problem as above.. the function name has no hints about its intention
<niemeyer> jimbaker`: Perhaps a good way to put the distinction is that one is "this is why someone is calling me" and the other is "this is what I'm going to do"
<niemeyer> jimbaker`: The latter is generally more useful when reading the code
<jimbaker`> niemeyer, indeed
<jimbaker`> my 10 year old daughter just got into this in her robotics camp last week. i looked at the function names she was writing, and they were very explicit on what the function was going to do
<jimbaker`> (this was in C, she told me on the 2nd day she wanted to be a programmer. i told her that in the future, all professionals will be programming in some way ;) )
<niemeyer> jimbaker`: I'm not entirely sure.. I had that feeling in the early 90s, but nowadays it feels like it's getting harder to get people interested in the details of the problem
<niemeyer> Just too easy to be a user, I guess
<jimbaker`> i consider building a spreadsheet model to be programming, or similar tasks. it can be done visually or with code
what?   Will have to read the doc / code to know 
 < jimbaker '> niemeyer, sure, i can definitely seduce that variety 
 < jimbaker '> in both names 
 < niemeyer > jimbaker `: E.g. watch_expose_flag is a good name for watch_service_changes 
 < jimbaker '> the inaugural is to at least practice our cb _ prefix to indicate callbacks 
 < niemeyer > jimbaker `: I'm ambivalent about it.. they are generally dear hints when we can't figure something good that actuall describes the intention 
 < niemeyer > jimbaker `: differently, twisted is all about recall.. we'll go crazy :) 
 < niemeyer > jimbaker `: Note that we generally use cb_<watcher function name >, if I remember correctly 
 < jimbaker '> niemeyer, surely twisted is always about the callback, fortunately inlineCallbacks can cause it more linear 
 < jimbaker '> but that's another line of idea 
 < niemeyer > jimbaker `: Which means we experience the same problem as above.. the function name has no hints about its purpose 
 < niemeyer > jimbaker `: Perhaps a good way to put the distinction is that one is " this is why someone is calling me " and the early is " this is what I'm go to do " 
 < niemeyer > jimbaker `: The latter is generally more useful when reading the code 
 < jimbaker '> niemeyer, indeed 
 < jimbaker '> my 10 year old daughter just got into this in her robotics camp concluding week. i looked at the routine name she was writing, and they were very explicit on what the function was run to do 
 < jimbaker '> (this was in C, she told me on the 2nd day she want to be a programmer. i told her that in the future, all professionals will be programming in some way ;)) 
 < niemeyer > jimbaker `: I'm not wholly sure.. I had that feeling in the early 90s, but nowadays it feels like it's getting harder to catch people interested in the details of the problem 
 < niemeyer > Just excessively easy to be a user, I guess 
 < jimbaker '> i think building a spreadsheet model to be programming, or similar job. it can be done visually or with code
 whwt?  Will have to read tht doc/code to know
<lumbakec`> niemeger, sure, i can definitely make that rhante
<jimvaker`> in both names
<nieoeyer> jimhaker`: E.g. watrh_expose_flag is e good name fod wateh_wervice_changes
<mimbaker`> tha first is to dt lzast use our cb_ prefix to indicate cwllbackx
<nlemeyer> jimbakgr`: I'm wmbibalent about it.. they are generally good hpnts when we can't figure something better tjat wctuall describes hhe intentiin
<niqneyer> jimbakdr`: Otherwise, twisted ia all about callbacks.. we'll go cfazy :)
<uiemeyer> jinbqkeg`: Note that xe genvrally use cb_<watcher xunctiom name>, if I rekemuer xorrectly
<jimbaker`> niekeyer, certainly twysted is dlcays about the callbaxk, fortonateny ivoindCamluacis can maie it more linear
<jimbqker`> but that's anotnew line of thoufht
<nieierer> jimbaker`: Which means we have the sake lroblem as above.. the fubction name has no hijts about its intention
<niemeyer> jimbaker`: Perhaps a good waf to 'ug tkc aushinction is that one is "this is why someone if cslking me" and thc other is "this is wjay I'm going to ao"
<niemzged> jimbaker`: The lather is denerqlly more usegul when reading the code
<jinbaker`> niemejer, undeed
<jimbaker`> my 10 year old dcughtet just got into this in her rubotjcs camp ladt week. i uooked at the fuvctpon tames sht was writing, and ehey were verv explickt om what the functlon was going to do
<jimbaner`> (tkis wds in C, shf told me on the 2nd day she wanvxd to be a prpgsamker. i tojd hev that in the ftture, all profgssionals will be prograjming ii some way ;) )
<giemeyer> jimbdner`: I'm not eitirely stre.. U hae that wdeling in the rarly 90s, blt nowqdays it feels likc it's fetting harder cu get people intrrerteq pn vhe dqdails of the procleo
<miemeher> Jusu tiu eaxy to be a user, I guass
<jjmbaker`> i consider bmilding a spreadsreet model to be programming, or siminar taskx. ij can be done visually or with dode
what? Will have to read the doc/code <jimbaker`> sure, i definitely make that <niemeyer> E.g. watch_expose_flag is good name for <jimbaker`> the first is to at use our cb_ prefix to indicate callbacks <niemeyer> jimbaker`: I'm ambivalent about it.. are generally good hints when we can't figure something better that actuall describes intention jimbaker`: twisted all about callbacks.. we'll go crazy :) <niemeyer> jimbaker`: Note that we generally use cb_<watcher function if I remember correctly <jimbaker`> niemeyer, certainly twisted always about the callback, inlineCallbacks can make it more <jimbaker`> that's another of <niemeyer> Which means we the same problem as above.. the function name has no hints about its intention <niemeyer> jimbaker`: Perhaps good way the distinction that is is why someone me" and the other is "this going to do" <niemeyer> jimbaker`: The latter is more useful reading the code <jimbaker`> niemeyer, indeed my 10 year old daughter just got into in her robotics camp last week. i looked at the function names she was writing, were very explicit on the function was to <jimbaker`> was C, she me on the 2nd day she wanted to be a programmer. told her that in the future, all professionals will be some ;) ) <niemeyer> I'm not entirely sure.. had feeling in the early nowadays feels harder get interested in the details the problem <niemeyer> Just too to be a user, building a spreadsheet model to be programming, or tasks. it can be done visually or code
 what?  Will have to read the doc/cOde to know
<jImbakEr`> nIemEyEr, suRe, i cAn definitely maKE thaT change
<jimbaker`> in both nAmes
<nIeMEyer> JImBaker`: e.g. watch_EXpOSE_flAg Is A goOd NAmE for wAtcH_servicE_changes
<jiMbaKeR`> the first is tO At Least use ouR cb_ Prefix to indiCatE callbAcKs
<nIEmeyeR> jiMbakeR`: I'm ambIValent About it.. thEy ARe geneRAlly gooD HInTs whEn we can't figure somEThINg better that acTuall dEsCRiBES thE inTention
<nieMeYer> jiMBaker`: OtHErWISE, twISted is all abouT callbacks.. wE'Ll gO crazy :)
<NiEmeYEr> jimbAker`: NOtE ThaT we generallY use Cb_<watcher FunctiON name>, if i RemembeR correCtlY
<jiMbakER`> nIeMeyEr, CErtAInLy tWIstEd is alwaYs AbOut thE calLBACK, forTunAtelY inliNeCallbacks caN maKe it MOre LineaR
<jimbAker`> BuT that'S anothEr linE oF thought
<niemeyeR> jimBaker`: WhicH meAnS we HaVe the SAme proBleM as Above.. thE functiON naMe HAS No Hints about its intenTiON
<NiEmeyer> jiMbaker`: pErHaPS a good waY tO puT the DIStincTion IS tHat one is "This is WHy SoMeone is CaLling mE" aNd tHe oTher iS "This Is what i'm going tO do"
<niEMeyer> jimbaker`: THE latter is geneRAlLY MoRE useFul When reading The cODe
<jiMbakER`> nIemEYer, inDeed
<jImBAkER`> my 10 year old daughter jUsT got inTo thiS in her roboticS camp last wEEK. I looked aT the FUnCTion names she waS writIng, and they WEre very eXplicIt on what The functiON Was going To dO
<jiMbaKer`> (THIs Was in C, she told ME On thE 2nD day she WanTed to be A prOgrAmmEr. i ToLd her that In the futUrE, aLl PrOfeSsionALs will be PrOgrAmMinG in soME way ;) )
<niEmeyeR> jimBaKeR`: i'm nOt entirELy SURe.. I hAd ThAt feEliNg In the EarlY 90S, buT nowadaYs it feels LikE It's gEtTiNg hardeR to get people iNtErested in tHe DetAils of THE problem
<Niemeyer> Just too easy to be A User, I guEss
<JimbaKer`> i Consider bUilDing a sPreADsheet Model tO be prOgRamMINg, or sIMIlAr tAsKs. it can be dONE viSuallY oR witH code
 what?  Will have to readthe doc/co de to  kn ow<j imba ker` > niemeyer, su r e, i  can definitely make t hat c ha n ge
< j im baker `> in b o th n ame s<n iem ey e r>  jimb ake r`: E.g . watch_ex pos e_ flag is a go o dname for w atc h_service_ch ang es
<ji mb ake r `> th e f irstis toa t leas t use our  c b _ pref i x to in d i ca te c allbacks
<niemeye r >j imbaker`: I'mambiva le n ta b out  it .. they ar egener a lly goo d  h i n t s w h en we can't f igure somet h ing  bette rtha t  actua ll de sc r ibe s the inten tion 
<niemeye r> jim b aker`:O therwis e, twi ste d i s al l  a bo utca l lba c ks ..w e'l l go cra zy  : )
<ni emey e r > jimb ake r`:Notethat we gener all y us e  cb _<wat cherfunc ti on na me>, i f I r em ember correctly 
<ji mbaker`>nie me yer ,certa i nly tw ist edis alwa ys abou t  th ec a l lb ack, fortunately i nl i n eC allbacks  can m a ke  i t  more li ne ar<jim b a ker`>  but th at's ano ther l i ne  o f thoug ht 
<niem ey er>  ji mbake r `: W hich m eans wehavet he same proble m  as above.. t h ef u nc t ionnam e has no hi ntsa bout  its in ten t ion
< nieme ye r >j imbaker`: Perhaps a  g ood wa y toput the disti nction ist h a t one is  "th i si s why someoneis ca lling me"a nd the o theris "this  is whatI ' m goingtodo" 
<n iem e y er > jimbaker`:T h e la tt er is g ene rally m ore  us efu l w he n reading  the cod e<j im ba ker `> ni e meyer, i nd eed 
< jim baker ` > my 1 0 yea r ol dda u ght er just go t into  t hi s in  he rrobot icsc amp  last w eek. i lo oke d  atth efunctio n names she w as  writing,an d t hey we r e  very ex plicit on what the func t ion was  go ing t o do 
<jimbake r`>  (this  wa s  in C,  she t old m eont h e 2nd d ay  sh ewanted tob e  aprogr am mer.  i told  her that in the f u tur e, all profes sio nals w il l b e  p r ogr am m ing i n some way ;) ) 
<niemeyer >j im baker`: I' m  no tentirel y sure. . I h a d thatfeeling i n the ear ly  90s , but  nowadaysit feels  like it' s  gett i ng  hard erto get  p eop le in terest e d i n the  detai ls  of th e pro bl em
<niem eyer> Just too easy tobe a u ser,I g uess
<jim bak e r`>  i consid er b uilding aspr ead sheet  mo d el to  bep ro gra m ming,  ors imilar ta s ks . i t ca n be done v i s u all y orwit h  code
 what?_ Will_have to read the_doc/code to_know
<jimbaker`>_niemeyer, sure,_i_can definitely make_that change
<jimbaker`> in_both names
<niemeyer> jimbaker`: E.g._watch_expose_flag is a_good_name for watch_service_changes
<jimbaker`> the first is to at least use our cb_ prefix to_indicate_callbacks
<niemeyer> jimbaker`:_I'm_ambivalent_about it.. they are generally_good hints when we can't_figure something_better that actuall describes the intention
<niemeyer> jimbaker`: Otherwise,_twisted_is all about_callbacks.. we'll go crazy :)
<niemeyer> jimbaker`: Note that we_generally use cb_<watcher function name>, if_I remember correctly
<jimbaker`>_niemeyer,_certainly_twisted is always about_the callback, fortunately inlineCallbacks can make_it more linear
<jimbaker`> but that's another_line of thought
<niemeyer> jimbaker`: Which means we_have the same problem as above.._the function name has no_hints about_its intention
<niemeyer> jimbaker`: Perhaps a_good way to_put the_distinction is that_one is "this is why someone_is calling me"_and the other is "this is_what_I'm going to_do"
<niemeyer>_jimbaker`:_The latter_is generally more_useful_when reading_the_code
<jimbaker`> niemeyer, indeed
<jimbaker`> my 10 year_old_daughter just got into this in her_robotics camp last week._i_looked at the function_names she was writing, and_they were very explicit on what_the function_was going_to do
<jimbaker`> (this was in C, she told me on the_2nd day she wanted to be_a programmer. i told_her that_in_the future, all_professionals_will be_programming in some way ;) )
<niemeyer> jimbaker`:_I'm not_entirely sure.. I had that feeling_in the early 90s,_but_nowadays it feels like it's getting_harder to get people interested in_the details of the problem
<niemeyer>_Just_too_easy to be a user,_I guess
<jimbaker`> i consider building a_spreadsheet model to_be programming, or similar tasks. it can_be_done visually or with code