Having the application flow decided on paper helps for me.
Once you know all the possibilities of the application, UI designing & coding pretty much fall into place. Definitely helps cover things that normally go unnoticed or overlooked when directly beginning with UI & code.
Having the application flow decided on paper helps for me.
Once you know all the possibilities of the application, UI designing & coding pretty much fall into place. Definitely helps cover things that normally go unnoticed or overlooked when directly beginning with UI & code.
Thanks!
But what about ways to plan out the coding? I've tried that with previous projects, but I've discovered that my code still gets out of hand and hard to manage. Any tips there?
Having a game plan before starting is always helpful. I usually have a few models done in UML. Usually some class diagrams to get a good idea of the hierarchies and modules involved. Maybe some behavioral diagrams to plot out the data and workflow.
As far as how I code my projects, modularizing code as much as possible gives me the best 'handle' over all of it. Small classes, lots of subclassing..
But what about ways to plan out the coding? I've tried that with previous projects, but I've discovered that my code still gets out of hand and hard to manage. Any tips there?
Class Diagrams!
Btw, changes are bound to happen, bt it helps to have the core structure of code neatly dealt with.