Ask HN:Do you go back and change your code or let it be.

#1

Post by ihaveaquestion » Mon, Sep 12, 2011, 10:10 AM UTC

After you learn better ways of implementing something do you go back and change it or let it be and make sure you do it the right way in the future.?

I ask this because I have this almost OCD urge to go back and change everything to perfection(or my idea of perfection at current!!).

EDIT: Added personal note.

Re: Ask HN:Do you go back and change your code or let it be.

#2

Post by madhouse » Mon, Sep 12, 2011, 10:38 AM UTC

Depends on the situation. If it makes sense to improve my code (it's still actively developed or maintained, and changing the implementation does not introduce incompability (or if it does, then it outweights the trouble of updating dependent software), etc), then I go back and change it. Otherwise, unlikely.

Re: Ask HN:Do you go back and change your code or let it be.

#3

Post by zura » Mon, Sep 12, 2011, 10:49 AM UTC

Depends. If it brings "childhood" memories, then let it be :)

Re: Ask HN:Do you go back and change your code or let it be.

#4

Post by dirkdeman » Mon, Sep 12, 2011, 1:03 PM UTC

I cringe whenever I come across a piece of code I've written years ago, but you know the old saying 'If it ain't broken...'. It also reminds me of where I came from as a coder.

Re: Ask HN:Do you go back and change your code or let it be.

#5

Post by scottshea » Mon, Sep 12, 2011, 1:45 PM UTC

Sometimes I do it to practice the new implementation and add/improve unit testing.