Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Even amongst engineers some concepts cannot be understood until you decide to “implement a replacement” from scratch. Around 60% of the way, you figure out your design and coincidently understand the design of the thing you previously didnt understand.

However during this journey, you may discover a better method. The other group also came to realise this, but since they invested so much into the origal design, they continue down that path. True refactoring only happens when disgruntled former employees decide to quit and reengineer the solution, this time they create a better product.



Sometimes it's better, sometimes it gets bogged down by the "second system effect" and is worse lol


Totally agree, and well run organizations will give authority to new teams to rebuild existing products, learning from the mistakes of the past while documenting their decisions along the way.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: