Timeline for When is a BIG Rewrite the answer?
Current License: CC BY-SA 2.5
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2019 at 0:31 | comment | added | visc | I think most people can do better the second time... Lots of code is written so fast anyways... I'm sure most people posting here make tons of mistakes and code that isn't solid... Humans + Time = Change | |
| Feb 4, 2019 at 14:57 | comment | added | Frank Hopkins | And why would I not do any better now that I've stepped once into every pitfall? Not to mention that most people learn over the time in general and re-evaluate their earlier decisions. | |
| Feb 4, 2019 at 14:54 | comment | added | Frank Hopkins | @Slawek Of course you can do more features / feature improvements when you improve on an earlier version than if you completely rewrite your basis in the same time, but that's not the point. The point is in longterm benefit. If MS had stayed with XP, would it ever have been able to deliver a Windows 7 / 10 with the functionality range and stability they have? Or could the legacy by that point have introduced so much bugs and be so unmaintainable that they struggled to keep up with integrating new hardware and plugging holes? A full rewrite is high cost now for reduced cost in the future. | |
| Feb 3, 2018 at 12:35 | comment | added | Brendan | @JᴀʏMᴇᴇ: Agreed - if you learnt nothing and gained no experience when implementing it the first time and/or if you can't do a better job now that you do have more knowledge/experience/hindsight; then you're a potato and not a programmer. | |
| Oct 9, 2013 at 12:51 | comment | added | JᴀʏMᴇᴇ | "...the truth is if the code was written by you - you won't be able to do any better." Would down-vote this post if I had enough rep. That's defeatest, unrealistic and implies that somehow people cannot progress to the point were the code they write is an improvement on code they wrote in the past. | |
| Nov 4, 2011 at 10:11 | history | made wiki | Post Made Community Wiki by user8 | ||
| Nov 4, 2011 at 10:09 | history | post merged (destination) | |||
| Jan 15, 2011 at 23:52 | comment | added | user1249 | XP is a vastly different codebase than ME. | |
| Jan 14, 2011 at 18:17 | comment | added | Slawek | Yes, these are good points. Microsoft rewrited winXP code and they couldn't even get file delete/copy right in first Vista retail version. While when they were just progressing their code base we're getting better quality constantly (W3.11=>W95=>W98=>ME=>XP), Vista in which they rewrote many core parts was a disaster. For new API... i'd separate the current code to have as much as i could intact, and use the new API on higher layer. Eg. your core classes stay as they are, but integration is done using new API. Unless everything is so messy that nothing else could be done than to start from 0. | |
| Jan 14, 2011 at 16:39 | comment | added | gideon | +1 I like your opinion, would like to know your thoughts about re-writing to a newer set of API? (See my answer below) | |
| Jan 14, 2011 at 16:32 | comment | added | Lukas Eder | Awesome, Slawek! extremeprogramming.org/rules/refactor.html | |
| Jan 14, 2011 at 14:25 | history | answered | Slawek | CC BY-SA 2.5 |