- Dec 17, 2017
- 7,426
- 9,702
Some software engineering advice for the team - first gather requirements, then do design, then code.
The earlier you find a problem, the cheaper it is to fix. Find a problem in requirements phase - super easy to fix. Find it in design phase, pretty easy to fix. Find it while coding, not too bad. Find it after you release, and you could have big problems.
How does this relate to the translation issue? Well, plan what you want, figure out how to do it, then do it. It seems like you had a vague idea of what you wanted to do, then started doing it, then realized you were going about it the wrong way.
Time spent in design is not a waste. It will save you much more time later when you're coding to the design instead of designing on the fly, and you realize that what you're trying to do doesn't quite work/fit.
The earlier you find a problem, the cheaper it is to fix. Find a problem in requirements phase - super easy to fix. Find it in design phase, pretty easy to fix. Find it while coding, not too bad. Find it after you release, and you could have big problems.
How does this relate to the translation issue? Well, plan what you want, figure out how to do it, then do it. It seems like you had a vague idea of what you wanted to do, then started doing it, then realized you were going about it the wrong way.
Time spent in design is not a waste. It will save you much more time later when you're coding to the design instead of designing on the fly, and you realize that what you're trying to do doesn't quite work/fit.