On Mar 19, 1:02 pm, "barry.b" <[EMAIL PROTECTED]> wrote: > see, that's my point - dodgy practices that slow development down, > especially if you're tasked to come in later and finish the pile of > rubbish. > > there should be no reason that people write bad** code, there's enough > code out there for people to appreciate and learn from...
I don't know about that. I've done lots of code reviews where the code was atrocious but the history behind the project wasn't that the developer didn't care.. more that the company didn't care. There's plenty of times people have been asked to knock up a prototype -- the equivalent of a couple of blocks of 2x4 and some big nails -- only to have that prototype wheeled into production by over eager managers. Most of us want to have the time to craft something exquisite but very often we're not given the chance to do so. This is especially a problem in the CF world where even the most mangled code manages to hang in there with some degree of functionality. Standards are great -- but when they're not followed its not always the developer at fault. Just thoughts... -- geoff http://www.daemon.com.au/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
