On 10/28/07, Alan Livie <[EMAIL PROTECTED]> wrote: > > > @Sam ... when you said 'I wasn't trying to claim that because we often > /can/ revisit code we can write it sloppily the first time around.' > > In my experience I never intentionally write 'sloppy code' but as I am > learning OO and Patterns I'm finding that even a month after writing certain > things I can see where it can be improved. > I only improve this code IF I have to work on it again to add a new > feature or fix an existing bug.
Excellent. That's what I'm getting at. As far as intentionally writing it sloppy - of course I understand you improve yourself over time (we all do!) and you can only do your best /at the moment/. It's good you are seeing improvement in your skills and can admit that code you wrote previously can be improved. Even better that you take the time to improve it when you work on it again. Intentionally writing it sloppy would be more of a case of "I don't have time to work on this right now, so I'm just going to create a big ball of mud and ship it." In our dev team we have started keeping a TODO: refactoring list with the > plan that we will gradually start with the highest priorities and work our > way through it (if management gives us the opportunity!). I'm sure this will > be a never-ending list :-) 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." The deadline was a firm one because it was a scheduled conference to which he had an invitation that may not happen again. We took on technical debt and made a similar list, but we never went back and improved the corners we cut. We might have done so at some point, but the plan was to do it within the week after the client demo to investors. We never did it a that point, nor in the final month we worked on it. It was then handed off, with the ugly code in it and I haven't worked on it since. We're starting to see that refactoring as we go adds more time to projects > but does cut down maintenance/bug fixing time. 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 =). Sam --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
