These are some 'nice to have' code design principles I'd like to try to put in, but we may not have time to completely flesh these out:
locking down most variables to private/protected unless really needed globally
minimizing direct calls into models from views (e.g. calling player's health from UI code)
setting up an observer system so views get updated automatically when models (i.e. health, abilities, enemy state) change.
moving all UI/Menu code to it's own module of objects so they can be better synced/maintained easier.
Since we're already at the end of this, there's an argument to be made that refactoring isn't that big of an issue. Good design makes it easier to understand/maintain/add features in, but we may not be adding anything substantial anymore. Might be a low priority since this doesn't deal directly with issues with features or bugs.
These are some 'nice to have' code design principles I'd like to try to put in, but we may not have time to completely flesh these out:
Since we're already at the end of this, there's an argument to be made that refactoring isn't that big of an issue. Good design makes it easier to understand/maintain/add features in, but we may not be adding anything substantial anymore. Might be a low priority since this doesn't deal directly with issues with features or bugs.