Скачать или смотреть Daniel Amber - Should you rewrite? @ DevConf Live 2020

Most of us have worked on or maintained a legacy codebase. We are forced to use older syntax or perhaps your framework has been deprecated and updating is near impossible without having to go sift through thousands of lines of code. The temptation to rewrite can be strong. The thought 'This would be so much better if it was done this way' can be more prominent than thinking about the years of business logic and refinement that has gone into an application. So it would seem that rewrites have their benefits but legacy code has often proved itself over the years. So the talk will address key issues such as 1) How do you know when to rewrite or perhaps, what sections of your codebase to rewrite? 2) How long should it take? 3) How do you position yourself in such a way that 10 years from now, you won't be in the same position you are today? At Cars.co.za we are currently working on a rewrite of our core product, which is one of South Africa's top 20 most visited sites. We have looked at issues that we have with our current codebase that we would like to change, but have also noticed good architecture and design decisions that we want to keep. We are in the rewrite phase and I would like to discuss the decisions that were made to get us to this point, and how we predict it will benefit us in the future.

This session was recorded at DevConf Live 2020 - for more information see www.devconf.co.za