best approach for this (besides recoding from scratch) is to migrate things slowly to a new/better structure every time you work on the project. if you see something wrong or that could be improved and have some time to fix it, do it... after a couple months you gonna have a better structured application...
if you are using a version control system like Git, create a parallel branch to implement the new structure to avoid breaking the deploy version, it's a really good workflow for complex projects: http://nvie.com/posts/a-successful-git-branching-model/ "don't live with broken windows": http://en.wikipedia.org/wiki/Broken_windows_theory a friend of mine recommended these books a couple months ago http://www.amazon.com/Refactoring-Improving-Design-Existing-Code/dp/0201485672 and http://www.amazon.com/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052/ but I haven't read them yet. good luck and remember: "An artist never really finishes his work; he merely abandons it" -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
