The question may seem trivial, but it is a real problem: when you are working on a project, do you do any architecture design before coding? Do you spend a lot of time working with the client to get detailed specifications / usecases / mockups?
During coding, do you change the architectural decisions that were made earlier? Do you come back to the client with a new set of specifications / usecases / mockups?
I am wondering what a good balance between all of these non-coding actions and the coding itself, from your experience?
Update:
So, from the anders, it seems so far that there are two approaches:
- design early, then sit and code to avoid late corrections.
- minimize part of the design, iterative development instead (agile methodologies seem to prefer it this way).
I think which way will depend on the project, team and client ... am I right?
source
share