On 10/27/07, Sam Larbi <[EMAIL PROTECTED]> wrote: > On 10/27/07, Barry Beattie <[EMAIL PROTECTED]> wrote: > > I used to be but I'm taking a more pragmatic approach now-a-days. > > Sending code into the big bad world, never to see it again, and having > > my reputation rest on it's success or otherwise. Get it right, get it > > out. > I'm not sure what you mean by that. Could you explain? (I know its off > topic from your original post, which is why I changed the subject, but I'm > interested nevertheless).
Without wishing to speak for Barry, I suspect he means that continuous improvement is a luxury you can afford when you will be working on the code throughout its lifetime. If you have just one shot to write code and release it to a client - and you won't get a chance to improve it after that - it had better be good, out of the gate! I agree. Code I write for myself and my startup (and to some extent for open source projects where I'll continue to be involved), I write fast and then refactor. Code I write for clients gets refactored during my time on the project but I aim to have it be as good as possible before I have to give it up. Make sense? -- 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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
