Assume a large body of existing work used across multiple websites: - No documentation - Buggy home-grown libraries (DB, connection pooling, strings, everything) - Home-grown "custom tag" system (parse the file on each page load) - Essentially un-maintainable and un-extensible
So... How do you deal with this situation? It takes too long to work on the existing codebase (I'd guesstimate a minimum 2-4x longer than a reasonable implementation, plus immeasurable developer irritation & frustration) for even the most minor of changes. Can you legitimately bill clients for work that should have already been done? Do you have to justify to every client the extra hours put in because of the current state of the app? _Can_ it be justified? Does it have to be an internal cost, and if so how can you generate momentum to get it done? Just curious. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
