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

Can you re-architect the product from scratch? This should be doable if the raw building blocks (modules etc.) are properly designed and easily incorporated into a new design. If this is not the case, then all the more reason to rewrite the code!


Over the years; I have found very few valid business reasons to re-write a code base that is still supporting the relevant business.

As a CTO, there is a good chance the poster would not be materially involved in such an effort.

From a business perspective; something that works is more important than something that is well architected.


Tell that to the Facebook team who recently rewrote their entire front end codebase using React.


I wonder, did they really rewrite or refactor. Did they chuck out every single last line of code at once, or transitioned it slowly? Do they no legacy code left at all?


I was also at FB when they hit File > New Project on their iOS app which IIRC drives more revenue than anything else at the company.


OP not enjoying the CTO role doesn't mean he/she should waste company resources for their own amusement.

http://www.joelonsoftware.com/articles/fog0000000069.html


Read carefully: I said only rewrite if the code structure is bad. If the code structure is good, then re-architecting can amount to restructuring only the top-level parts.

It can give OP a better feel for how the code is designed, and give them more opportunity to change things in a more structured way in the long term by repeating the process (rather than just fighting fires every time).


Code structure provides very little business value.

Ten year old battle tested spaghetti is more valuable than any benefits a complete re-write would provide.




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

Search: