On Aug 22, 11:21 pm, RobG <[EMAIL PROTECTED]> wrote:
> On Aug 23, 4:31 am, dhtml <[EMAIL PROTECTED]> wrote:
> [...]
>
> > As with any subject, there is always more to be discovered and
> > discussed. I think there is more to be said, and particularly with
> > what I wrote here:-
>
> > | That [internal quality would matter only to developers] is true
> > | because poor internal quality means the code is harder to
> > | change and modify.
>
> > That is questionable and possibly wrong (yes I wrote it). Pity that
> > the only response that elicited seemed so braindead.
>
> To a large extent it is correct: users don't care about the underlying
> quality of the code as long as it meets their requirements. But if
> you care about maintenance, it is a very big concern.
>
> Poor code affects users when it comes time to upgrade their platform -
> suddenly things don't work and they get charged a fortune to fix the
> issues.
I've seen enough sites break in Firefox 3. Comcast live chat support
feature, for example.
New feature requests will require working with the existing code. If
the code is messy, then the new feature will take longer.
Code quality affects business, too.
>
> --
> Rob
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"iPhoneWebDev" 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/iphonewebdev?hl=en
-~----------~----~----~----~------~----~------~--~---
