tag:blogger.com,1999:blog-6628985022531866193.post7785261978249324271..comments2024-02-12T17:37:05.629+00:00Comments on The OldWood Thing: TODO or TODO Not - There Is No LaterChris Oldwoodhttp://www.blogger.com/profile/18183909440298909448noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-6628985022531866193.post-12715905078629587202011-10-02T07:50:23.166+01:002011-10-02T07:50:23.166+01:00Guilty...
and I have optional build time noise vi...Guilty...<br /><br />and I have optional build time noise via a custom #pragma (which has been turned off in most of my builds for a long time now, enough said)... <br /><br />I now try and include the JIRA ticket number in the TODO, and I try and cull them at various 'stage complete' points in the development.Len Holgatehttp://www.lenholgate.comnoreply@blogger.comtag:blogger.com,1999:blog-6628985022531866193.post-55847523121265241682011-09-22T12:23:24.313+01:002011-09-22T12:23:24.313+01:00I do use TODOs (although I call mine !TBD, to make...I do use TODOs (although I call mine !TBD, to make sure they are distinguished from those that may be generated).<br /><br />As a general rule I only use them as I'm writing code and I know I need to add something, but it's not necessary to get the code running/ test passing right now.<br />It's at that point that I have the pieces in my head to know what should go there, but if I was to do it there and then it would break my flow - and be superflous to the task at hand. If I don't write it as a !TBD then I'll lose valuable context that must be regained when I do have to come back to it.<br /><br />Of course when I do come back I may have a valuable new context, or updated knowledge, that invalidates or extends what I originally wrote - but that's ok. I now have the benefit of *both* contexts to make my decisions on.<br /><br />I try not to check !TBDs in. This rule could be stricter, but in practice it's easier to check in as soon as my immediate task is complete - !TBDs and all - then, as a follow-on go back and review the !TBDs I introduced. Either convert them to tests, fix the code, log an issue or whatever.<br /><br />That's the theory - and it bears some similarity to reality.<br />In practice, of course, that would take far too much discipline! So crufty !TBDs can tend to build up. I usually bump into them soon enough - either accidentally, or by grepping for !TBD - and either rip them out or follow one of the other practices I mention. So they don't hang around for too long.<br /><br />Except when they do.Phil Nashhttp://www.levelofindirection.comnoreply@blogger.comtag:blogger.com,1999:blog-6628985022531866193.post-31149508273156192342011-09-22T12:12:25.024+01:002011-09-22T12:12:25.024+01:00I mostly agree - but not entirely.
// TODO: expla...I mostly agree - but not entirely.<br /><br />// TODO: explain whyPhil Nashhttp://www.levelofindirection.comnoreply@blogger.comtag:blogger.com,1999:blog-6628985022531866193.post-78852877430128500662011-09-22T09:25:22.364+01:002011-09-22T09:25:22.364+01:00Yes, I fully agree and I go further, don'e use...Yes, I fully agree and I go further, don'e use TODO ever... <a href="http://marcin.floryan.pl/blog/2010/03/todo-or-not-to-do" rel="nofollow">TODO or not to do</a>Marcinhttps://www.blogger.com/profile/13124079306935692892noreply@blogger.comtag:blogger.com,1999:blog-6628985022531866193.post-563275148769718682011-09-22T08:44:50.045+01:002011-09-22T08:44:50.045+01:00Agreed!
The catch clause is a beautiful example o...<a href="http://wordaligned.org/articles/todo" rel="nofollow">Agreed!</a><br /><br />The catch clause is a beautiful example of the damage todo can do.Thomas Guesthttp://wordaligned.orgnoreply@blogger.com