4 ms·
A great writeup! A lot of startups face the situation that you need to do significant architectural changes to pay the technical debt and re-enable development
by dirtyaura 9y ago
A great writeup! A lot of startups face the situation that you need to do significant architectural changes to pay the technical debt and re-enable development speed, or improve the performance and scalability of the service. At the same time, stopping feature development altogether for months is impossible.
Incremental rewrite is often the only way to go. I liked how you approached the rewrite with adapters. I'd be very interested if somebody would collect these kind of "rewrite war stories" to a book form and maybe synthesize common patterns from the stories.
- pspeter3 9y agoThanks! We would have really appreciated a resource like that when we started the process. We wanted to share our story in case it is helpful to others.
- awhitty 9y agoI would love a resource like that! We went through a very similar process on my team [0], and I was pleased to see this post validating some pain points we had seen. > In hindsight, we chose the correct trade off. This is key, and I think it's almost something you have to blindly follow when going into the transition. It's a lot easier to justify the decision to incrementally rewrite in retrospect than it is to get excited about it in the process. I think more examples would help shift that. [0]: https://heap.engineering/migrating-react-mobx-while-shipping-new-features/ https://heap.engineering/migrating-react-mobx-while-shipping...