4 ms·
Sorry, but this is really bad advice. It is very tempting to redo something from scratch, but in doing so you will end up spending a very large amount of time f
by vineet 14y ago
Sorry, but this is really bad advice. It is very tempting to redo something from scratch, but in doing so you will end up spending a very large amount of time fixing issues and adding details that were already done in the original code.
- antidoh 14y agoI think the advice was sarcastic.
- vineet 14y agoOh, In that case... (I can't tell you how many times I have heard the same advice being given seriously)
- antidoh 14y agoSame.
- TillE 14y agoIt can sometimes be the right approach. It's not a decision to be taken lightly, but it should be on the table. Especially if your goal is not to duplicate the functionality of the old software precisely, but to provide a significant upgrade. It really depends on the requirements.
- cjdentra 14y agoOh yes, I have seen where re-writes are actually done. Developers start to talk about the lack of "scalability" and "maintainability" of the application with the best solution being to rewrite the app. I've also seen Java-to-Microsoft stack ports being bandied about. Generally it is a really bad idea but some of the decision depends on the language(s) preferred by the firm inheriting the app and the size of the app.