Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #60615
| From | Mark Lawrence <breamoreboy@yahoo.co.uk> |
|---|---|
| Subject | Re: Use of logging module to track TODOs |
| Date | 2013-11-27 15:13 +0000 |
| References | <0f0dc3b6-1c06-4c76-99ba-8df4969d6ee2@googlegroups.com> <2056962806.47363143.1385563961849.JavaMail.root@sequans.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.3304.1385565236.18130.python-list@python.org> (permalink) |
On 27/11/2013 14:52, Jean-Michel Pichavant wrote: > > > ----- Original Message ----- >> Hey list, > > Greetings ! > >> How do you do with your TODOs? >> >> Regards, >> Jordi > > TODOs always share the same fate : they get forgotten and wander the code until the project dies. Unless you have the required mental resilience to stop the urgent work to fix your TODOs once a week, this is gonna happen. > > Here's how I'm dealing with TODOs: > 1/ I instantly remove them. > 2/ I force myself to fix them right now, when possible, If not, I'll have to live without. > > At least, it works for me. > > JM > > Note : fixing the TODO right now is efficient as you don't need to switch your working context a few weeks later. > This, from the Zen of Python, seems applicable in this context. Now is better than never. Although never is often better than *right* now. -- Python is the second best programming language in the world. But the best has yet to be invented. Christian Tismer Mark Lawrence
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Use of logging module to track TODOs Jordi Riera <kender.jr@gmail.com> - 2013-11-27 06:38 -0800 Re: Use of logging module to track TODOs Mark Lawrence <breamoreboy@yahoo.co.uk> - 2013-11-27 15:13 +0000
csiph-web