3 ms·
Can't afford to start again every 5 years. I Beg to differ, or at least add more perspective. I've noticed a trend over the past few years at large (>1$bn re
by krona 8y ago
Can't afford to start again every 5 years.
I Beg to differ, or at least add more perspective. I've noticed
a trend over the past few years at large (>1$bn revenue) b2b and telecoms companies; teams in those organisations working on newer projects or initiatives start with the premise that the UI will be rewritten again in 3-5 years, and design accordingly. Maintenance concerns of that part of the project, for good or bad, melt away.
- setquk 8y agoI think you need to ask the end users their opinion of this. This is a common failure mode in corporations of that size. It's really not efficient throwing everything away every 3-5 years. 10 years is minimum cycle IMHO, possibly longer now that standards are relatively stagnant allowing incremental improvement. That's the point at which you can recoup the retraining investment and cover the hardware cycles easily. At the end of the day the purpose of the software is to deliver a benefit and churn based rewrites pretty much pause all comprehensive development projects. They have no business value.