Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • Awesome, Slawek! extremeprogramming.org/rules/refactor.html Commented Jan 14, 2011 at 16:32
  • +1 I like your opinion, would like to know your thoughts about re-writing to a newer set of API? (See my answer below) Commented Jan 14, 2011 at 16:39
  • 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. Commented Jan 14, 2011 at 18:17
  • 1
    "...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. Commented Oct 9, 2013 at 12:51
  • 1
    @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. Commented Feb 3, 2018 at 12:35