I do something similar to this, in either comments within the code or the the block of comments at the top of my pages I will put in ToDoFlags. Whenever I come across them if I need to revisit the page then I will typically either do it at that time or at least re-evaluate if it needs to be done. Then whenever I may have some time for a project that needs nothing done to it then I will search the site for ToDoFlags and pull those up to see what I can knock out. I am just not using Eclipse for this, something I started to do years ago and maintained and used whatever extended find feature my current IDE of choice allows me to find the flags. The scanning for things to do tends to be a rare occurrence though simple due to my time schedule.
On 10/28/07, Sean Corfield <[EMAIL PROTECTED]> wrote: > > > On 10/28/07, Sam Larbi <[EMAIL PROTECTED]> wrote: > > Awesome. Does anything ever get done on this todo list? On a somewhat > > recent project, we cut a few corners because the client wanted to show > > potential investors sooner than we could "do it right." > > I add TODO comments to the code wherever I need to revisit something > and then I can just look at the task list in Eclipse and jump straight > to any code. Since the task list is always present in Eclipse, it acts > as a good reminder that stuff needs to be done. > > Mostly, whenever I touch code that contains a TODO comment, I will > check if it's something I have time to fix while I'm fixing something > else. Only yesterday, I was adding a whole new workflow to scazu.com > and, due to a shift in focus from our original launch in July, we now > have some "badly" named methods in the "wrong" service components and > a couple of our database tables also have "bad" names. Adding the new > workflow touched a lot of the code that referred to the old, > misleading names so it was a reasonable trade off to bite the bullet, > create a new service component, move and rename a few methods and then > change the DB table alias in the transfer.xml file (I love Transfer > because it makes this sort of refactoring so easy!) and just update > the set/get/hasParentFoo() method calls to set/get/hasParentBar() > across the application. It probably took 30 minutes out of a total 8 > hours of work on the workflow but the result is much more maintainable > code because the names of key entities and methods are much less > misleading now. > > > Ahhh, but maintenance and bug fixing are part of projects! Maybe not > the > > part you have to work on, but someone has to pay that cost =). > > Very much so. If you're handing off code to clients, you want to pass > on as little technical debt as possible to them. Carrying technical > debt for yourself is a slightly different set of trade offs. > -- > Sean A Corfield -- (904) 302-SEAN > An Architect's View -- http://corfield.org/ > > "If you're not annoying somebody, you're not really alive." > -- Margaret Atwood > > > > -- Aaron Rouse http://www.happyhacker.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
