Version 2.0
futility
Registered User, ClubPA regular
Registered User, ClubPA regular
I have a database that I built with a team, we all basically taught ourselves filemaker and went from there. Now because we have no formal training in how things are supposed to be, we get into arguments.
This summer we should be upgrading our work. Our argument now, which I don't know what's right or normally done is... do we start clean and build a new database and import the old info into the new OR fix all our problems and messes we with our original database?
This summer we should be upgrading our work. Our argument now, which I don't know what's right or normally done is... do we start clean and build a new database and import the old info into the new OR fix all our problems and messes we with our original database?
futility on
0
Posts
I would start by getting together and discussing the following:
1) How much is there to fix?
2) How hard is it to fix - some problems are easy to fix, some are troublesome in a system due to the fix requiring to you to also change many other things.
3) How much time and effort would it take to rewrite?
4) What would you gain from a full rewrite vs just fixing a bunch things? A rewrite can offer an entirely better architecture which may offer better performance, easier to maintain, easier to add new features to, etc. Fixing, on the other hand, can be done in small sections at a time, allowing you to release smaller, more frequent changes rather than having to wait for the whole rewrite thing to be done and ready to go and, hopefully, you can re-use more of the code than not and so it could be much quicker.