Lessons learned from rewriting code

Re:Lessons learned from rewriting code by rightbyte on Saturday June 15, 2019 @01:54PM (#20191183)

Iterational design is a thing.

If the same team that did the crappy code gets a chance to learn from the mistakes and rewrite it part by part now when they have the whole picture, it's easier and the end result might be mantainable and nice.

[ Parent | on HN ]

Re:Lessons learned from rewriting code by marcinzm on Saturday June 15, 2019 @02:05PM (#20191248)

I've heard that the worst code is the 2nd version. You try to fix everything from the 1st version (real or perceived) and over correct as a result.

[ Parent | on HN ]

Re:Lessons learned from rewriting code by hpolatyuruk on Sunday June 16, 2019 @05:57AM (#20194751)

Yes, I've heard that too. But in our rewriting case, it didn't happen. We didn't make that mistake. Usually, developers made a lot of mistake in the first version and they learned many lessons. Now they are experienced about software and they will try to implement everything in the 2nd version. And they will come up with the complex system again. In our case, we cut off many features and we kept our code base small.

[ Parent | on HN ]

Re:Lessons learned from rewriting code by bdavis__ on Saturday June 15, 2019 @02:58PM (#20191500)

However the third iteration is something that you can be proud of. (but in my experience, 1/2 through the second iteration the funding gets cut off)

[ Parent | on HN ]