For reasons it’s not worth getting into, the object Model of the django application I am working on is now “wrong” insofar as a number of relations that are 1 to Many are represented as Many to Many. The application functions correctly and is most of the way through QA. It has never been deployed.
My design OCD makes me want to refactor it to correct the problem The only good time to do it is now, before it goes into production, but it’s still not that good a time as QA would have to be redone and the project would slip.
Are there any good engineering reasons to do the refactoring? This is a tool which will have a user base numbered in the tens rather than the tens of thousands and the database is unlikely to grow to significant size in the short to medium, probably even the long term. I strongly doubt performance is going to be a factor.
The only business reason I’d potentially see to justify redoing the QA is maintainability. My questions would be:
If you refactor now, you’ll take a short term productivity hit at the potential benefit of long term productivity gains, since the simplicity gained will probably improve maintainability. There is no right answer, though – it really depends on how your project and deployment is setup, and how your software will be used.