I concur. And if it cannot be hold simple or is dependant on multiple sources throughout the developing-phase then a Bus Factor (http://en.wikipedia.org/wiki/Bus_factor) is a must. I've often seen architecture-models for eCommerce who weren't bad from a customer's view but so complicated structured that even the well-seasoned "maintainer's" had troubles to add additional code or edit it.
It's worth a lot more to invest time into planning your architecture to avoid headaches later on. If not for you, then for the person who has to maintain the code when you're gone.
I concur. And if it cannot be hold simple or is dependant on multiple sources throughout the developing-phase then a Bus Factor (http://en.wikipedia.org/wiki/Bus_factor) is a must. I've often seen architecture-models for eCommerce who weren't bad from a customer's view but so complicated structured that even the well-seasoned "maintainer's" had troubles to add additional code or edit it.
It's worth a lot more to invest time into planning your architecture to avoid headaches later on. If not for you, then for the person who has to maintain the code when you're gone.