 continue to follow those left-hand turns, writing or updating article after article, until eventually I wind up back where I started.

If one of those pages is missing an example, odds are good it’ll be hard to resist creating one, although if it will take more than a few minutes, this is where I’m likely to reluctantly flag it for someone else to do later, unless it’s really interesting and I am just that intrigued.

By the time I’m done documenting <dial>, I may also have updated badly out of date documentation for three other elements and their interfaces, written pages about how to decide on the best way to represent your data, added documentation for another undocumented element that has nothing to do with anything but it was a dead link I saw along the way, updated another element’s documentation because that page was where I happened to go to look at the correct way to structure something, and I saw it had layout problems…

You get the idea.

How I have to do it now

Unfortunately, I can’t realistically do that anymore. We have adopted a system of sprints with planned work for each sprint. Failing to complete the work in the expected amount of time tends to get you dirty looks from more and more people the longer it goes on. Even though I’m getting a ton accomplished, it doesn’t count if it’s not on the sprint plan.

So I try to force myself to work on only the stuff directly related to the sprint we’re doing. But sometimes the line is hard to find. If I add documentation for an interface, but the documentation for its parent interface is terrible, it seems to me that updating that parent interface is a fairly obvious part of my job for the sprint. But it wasn’t budgeted into the time available, so if I do it, I’m not going to finish in time.

The conundrum

That leaves me in a bind: do strictly what I’m supposed to do, leaving behind docs that are only partly usable, or follow at least some of those links into pages that need help before the new content is truly usable and “complete,” but risk missing my expected schedule.

I almost always choose the latter, going in knowing I’m going to be late because of it. I try to control my tendency to keep making left turns, but sometimes I lose myself in the work and write stuff I am not expected
continue to follow those left - hand turn, write or updating article after article, until finally I wind up back where I start. 

 If one of those pages is missing an model, odds are good it ’ll be hard to defy creating one, although if it will take more than a few minute, this is where I ’m likely to reluctantly flag it for someone else to act subsequently, unless it ’s really interesting and I am just that intrigued. 

 By the time I ’m done documenting < dial >, I may besides have updated badly out of date documentation for three early elements and their interfaces, written pages about how to decide on the best manner to represent your data, added documentation for another undocumented element that give birth nothing to do with anything but it was a dead link I saw along the way, update another element ’s documentation because that page was where I happened to go to look at the correct way to structure something, and I saw it had layout problems … 

 You have the idea. 

 How I have to do it nowadays 

 Unfortunately, I ca n’t realistically do that anymore. We have adopted a system of dash with planned workplace for each sprint. Failing to dispatch the work in the expected amount of time tends to get you dirty looks from more and more people the longer it goes on. Even though I ’m getting a ton carry through, it does n’t count if it ’s not on the dash design. 

 therefore I try to force myself to work on merely the stuff directly related to the dash we ’re doing. But sometimes the cable is hard to find. If I total documentation for an interface, but the software documentation for its parent interface is terrible, it seems to me that updating that parent interface is a fairly obvious part of my occupation for the sprint. But it was n’t budget into the time available, so if I do it, I ’m not rifle to finish in time. 

 The riddle 

 That leaves me in a bind: do strictly what I ’m supposed to do, leaving behind docs that are only partly usable, or follow at least some of those links into page that need help before the modern content is truly functional and “ complete, ” but risk missing my expected schedule. 

 I almost always choose the latter, going in knowing I ’m going to be belated because of it. I sample to operate my tendency to keep making left turns, but sometimes I lose myself in the employment and write stuff I am not expected
 cojtinue to follow those ltft-hand turns, wrijibg or npdatinf articld after article, until eventuelly I wibd up back where I stafted.

If onv of thosw pajes is missing ai examplc, odda are jood it’ll be hatd to resist creating one, dlghlugh if it will take more than a fer minutrs, this is where I’m kykelg to reluctantly flag it for someohe else to do later, inless it’s really interestlng wnd I am just that intrigued.

Bi thq time I’m dond documentpug <dial>, I mzy also have updated badly out uf dace documentqtuon xor three ovher ejements and bneir itterfacrs, written pagcs abmut how to decide on the best way to reprefent your dcta, added documentatiin for dnotver jbdozumtntxd slemenh tiat has notging to do qith anything but iu www a dead link I saw ajong the way, updated another element’s dmcujentation because that page was where I happgned to go to look at the correct way to structure somethinc, and K scq it fqd layout problems…

You get the idea.

How I have to so in now

Unfortunateln, I can’t realisticslpy qo that anymote. We hcbe adopted a system lf sprigts wuth planntd wotk for each sprint. Failing ro complete nhe qork in the expectzd amount of timg tendx to get you dirty lookr frkm more and more peolue the longer it govs ot. Even though I’m getting a ton acconplixhed, it doexn’t cotnt if it’s not on the sprint plan.

Sl I tty to xorce mysepf to work on only the stuff dicxctly related tm tve sprinc we’re doing. But soietimes the liue is haxd to wind. If I zdd docnmentation fjr an interfawg, but the docnmentatiog foe itw pareng interface is yerrible, pt seens to me that updabing jhzt parent interycct us a fairly obfiojs [agt pf ky job for tve sorivy. But it wasn’t bmdgdted into the time availdble, so if I do it, I’m mob going ti finish in time.

The cpnundrum

That leaved me mn a bmnd: do sttictly what I’m supposed to do, lsaving bejinq docs that wre inly partly bsable, or follow at least some of those oinks into pages jhat need help before uhe new conteit is eruly usatle and “complete,” but risk missing my txpected schedule.

I almoat alwdys cjoose the latter, going in knowing I’m going to be late because of it. I try to coitwol my tendsncy to kvep kaking lefv vurns, but sometimvs I lose myself in the work and write sduyf I am not expected
continue to follow those left-hand turns, writing article article, until I wind up one those pages is an example, odds good it’ll be hard to resist one, although if it will take more than a few minutes, this is I’m likely to reluctantly flag it for someone else to do later, unless really and am that intrigued. By the time I’m done documenting <dial>, I may also have updated badly out date documentation for three other elements and their written pages about how decide on the best way represent data, added for undocumented that has nothing do with anything but it was a dead link I saw along the way, updated another element’s because that where I to to at the correct structure something, and I saw it You get the idea. How I have to it now I can’t realistically do that anymore. have adopted a system of sprints with planned for each sprint. Failing to complete the work in the expected amount of time tends you dirty looks from and more people longer goes Even I’m getting ton accomplished, it doesn’t count if it’s not on the sprint So I try to force myself to work on only directly to the sprint doing. But sometimes the is to find. If I for interface, for parent is terrible, it seems me that updating that parent is a fairly obvious the sprint. But it wasn’t budgeted into the available, so if I do it, I’m going to finish in time. The conundrum That leaves me in a do strictly supposed to do, leaving behind docs that are partly usable, or follow least some of those links into pages that need before new content truly usable and but risk missing expected schedule. I choose the going knowing be late because of it. I to my tendency to keep making turns, I lose myself in the work and write stuff I am not expected
 continue to follow those left-Hand turns, wRitinG or UpdAtIng aRticLe after article, UNtil Eventually I wind up back wHere I StARted.

iF oNe of tHose pagES iS MIssInG aN exAmPLe, Odds aRe gOod it’ll Be hard to reSisT cReating one, alTHoUgh if it wilL taKe more than a fEw mInutes, ThIs iS Where i’m lIkely To reluCTantly Flag it for SoMEone elSE to do laTER, uNlesS it’s really interesTInG And I am just that IntrigUeD.

by THE tiMe I’M done documEnTing <dIAl>, I may aLSo HAVE upDAted badly out oF date documeNTatIon for ThRee OTher elEmentS aND thEir interfacEs, wrItten pageS about HOw to decIDe on the Best waY to RepReseNT yOuR daTa, ADdeD DoCumENtaTion for aNoThEr undOcumENTED eleMenT thaT has nOthing to do witH anYthiNG buT it waS a deaD linK I Saw alOng the Way, upDaTed another elemeNt’s dOcumentatIon BeCauSe That pAGe was wHerE I hAppened To go to lOOk aT tHE COrRect way to structure SoMEThIng, and I sAw it haD LaYoUT problemS…

YOu gEt thE IDea.

HoW I haVE tO do it now

unfortUNaTeLy, I can’t ReAlistiCaLly Do tHat anYMore. we have Adopted a SysteM Of sprints with pLAnned work for eACh SPRiNT. FaiLinG to complete The wORk in The eXPeCteD AmounT of tiMe TEnDS to get you dirty looks FrOm more And moRe people the loNger it goes ON. eVen thougH I’m gETtINg a ton accompliShed, iT doesn’t couNT if it’s noT on thE sprint pLan.

So I try TO Force mysElf To wOrk On oNLY tHe stuff directLY RelaTeD to the sPriNt we’re dOinG. BuT soMetImEs the line Is hard to FiNd. if i aDd dOcumeNTation foR aN inTeRfaCe, but THe docuMentaTion FoR iTS paRent intERfACE is tErRiBle, iT seEmS to me That UPdaTing thaT parent inTerFAce iS a FaIrly obvIous part of my jOb For the spriNt. but It wasn’T BUdgeted iNto the time available, so if i Do it, I’m nOt gOing tO finIsh in time.

the ConundRum

tHat leaVes me iN a binD: dO stRICtly wHAT I’M suPpOsed to do, leAVIng BehinD dOcs tHat are oNly partly usable, or fOLloW at least some oF thOse lINKs IntO PaGEs tHaT NeeD HElp before the new Content is tRuLY uSable and “coMPleTe,” But risk Missing My expECted schEdule.

I almOst always ChOose THE laTter, going iN knowing i’m going to BE late BEcAuse oF it. i try to CoNtrOl my tEndencY To kEep maKing leFt Turns, bUt somEtImes I losE myself in the work and writE stuff i am noT exPected
 continue to follow thoseleft-handturns , w rit in g or  upd ating articlea fter  article, until eventu allyIw indu pbackwhere I st a r ted .
I f o ne of  thos e p ages is  missing a n e xa mple, odds a r egood it’ll  be  hard to res ist  creat in g o n e, al tho ugh i f it w i ll tak e more th an a fewm inutes, t hi s is  where I’m likely to reluctantly fl ag itfo r  s o m eon e e lse to dola ter,u nless i t ’s r e all y  interestingand I am ju s t t hat in tr igu e d.

By  theti m e I ’m done doc umen ting <dia l>, Im ay also have up datedbad lyouto fda tedo c ume n ta tio n  fo r threeot he r ele ment s a n d th eir  int erfac es, written p age s ab o uthow t o dec ideon  thebest w ay to  r epresent your d ata,  added do cum en tat io n for anothe r u ndo cumente d eleme n t t ha t h as  nothing to do wit ha n yt hing but  it wa s  a  d e ad linkIsaw  alo n g  theway, up dated an othere le me nt’s do cu mentat io n b eca use t h at p age wa s whereI hap p ened to go tol ook at the co r re c t  w a y to  st ructure som ethi n g, a nd I sa w i t  hadlayou tp ro b lems…

You get theid ea.

H ow Ihave to do it  now

Unfo r t u nately,I ca n ’t realisticallydo th at anymore .  We have  adop ted a sy stem of s p r ints wit h p lan ned  wo r k  f or each sprin t .  Fai li ng to c omp lete th e w ork  in  th eexpectedamount o fti me  t end s tog et you d ir tylo oks  from more a nd mo re p eo pl e  th e longe r  i t goes  o n.  Eve n t ho ugh I ’m g e tti ng a to n accompl ish e d, i tdo esn’t c ount if it’sno t on the s pr int  plan. So I try  to force myself to wor k  on onl y t he st uffdirectlyrel ated t o t h e spri nt we’ re do in g.B u t som e t im esth e line ish a rdto fi nd . If  I adddocumentation fora n i nterface, but  th e do c u me nta t io n  fo ri tsp a rent interfaceis terribl e, it  seems tom e t ha t updat ing tha t par e nt inte rface isa fairlyob viou s par t of my jo b for th e sprint. But i t  w asn’t  bu dgeted  i nto  thetime a v ail able,  so if  I  do it , I’m  n ot going  to finish in time.

Th e conu ndrum 

T hat leave s m e  in  a bind:do s trictly wh atI’m  supp ose d  to d o, l e av ing behin d do c s that ar e  o nly p ar tly usable, o r  fo llowatl east s omeof those links in t o pages that n eedh e lpbef o re t he  new content i s t ru l y  usablean d “complete ,” but r is k  miss ing my  expec ted sch e d ul e .

I a lmos t a lways cho ose  t h e latte r,  g o ing in  kno wi ng I’m  going to b e late because ofit. I t ry to con trolmy  tenden c y to  keep maki ng left tur ns, bu t so metim es I lo se  mysel f i nthe work a n d write s tuffI am no texpe cte d
 continue_to follow_those left-hand turns, writing_or updating_article_after article,_until_eventually I wind_up back where_I started.

If one of_those pages is_missing_an example, odds are good it’ll be hard to resist creating one, although if_it_will take_more_than_a few minutes, this is_where I’m likely to reluctantly_flag it_for someone else to do later, unless it’s_really_interesting and I_am just that intrigued.

By the time I’m done documenting_<dial>, I may also have updated_badly out of_date_documentation_for three other elements_and their interfaces, written pages about_how to decide on the best_way to represent your data, added documentation_for another undocumented element that has_nothing to do with anything_but it_was a dead link I_saw along the_way, updated_another element’s documentation_because that page was where I_happened to go_to look at the correct way_to_structure something, and_I_saw_it had_layout problems…

You get_the_idea.

How I_have_to do it now

Unfortunately, I can’t_realistically_do that anymore. We have adopted a_system of sprints with_planned_work for each sprint._Failing to complete the work_in the expected amount of time_tends to_get you_dirty looks from more and more people the longer it goes_on. Even though I’m getting a_ton accomplished, it doesn’t_count if_it’s_not on the_sprint_plan.

So I_try to force myself to work on_only the_stuff directly related to the sprint_we’re doing. But sometimes_the_line is hard to find. If_I add documentation for an interface,_but the documentation for its_parent_interface_is terrible, it seems to_me that updating that parent interface_is a fairly_obvious part of my job for the_sprint._But it wasn’t budgeted into the_time_available, so if I do it,_I’m_not_going to finish in time.

The_conundrum

That leaves me in a bind:_do strictly what I’m supposed to do, leaving behind_docs that are_only partly usable, or follow_at_least_some of those links into pages that need help before_the new_content is truly_usable and “complete,” but risk missing my expected schedule.

I almost_always choose the latter, going in knowing_I’m going to be late because of it. I try to_control my tendency to keep making left turns,_but sometimes I lose myself in the_work and write stuff_I_am not expected