Description
Making widespread changes to a codebase can be hard! Your team starts a long-lived branch that is difficult to maintain and often impossible to merge; you and your team-mates agree to improve the code slowly over time, but you all forget this agreement, and the improvement never happens. But what if there were a tool that keeps you on track to steadily improve your code without making you feel like losing control over these improvements?
Today we talk with Craig Spence, a senior engineer at Spotify and a creator of Betterer - a tool that helps with incremental improvements of big codebases and legacy systems. Craig tells us how Betterer works, how it differs from other debugging tools, and what are the plans for its improvements.
When you finish listening to the episode, connect with Craig on LinkedIn and Twitter, and be sure to check out Betterer on GitHub.
Mentioned in this episode:
Craig on LinkedIn at https://www.linkedin.com/in/craig-spence/
Craig on Twitter at https://twitter.com/phenomnominal
Betterer on GitHub at https://phenomnomnominal.github.io/betterer/docs/introduction
Touca at https://touca.io
There are three groups of people around every legacy system - those who are stuck with it, those who don't want to be with it, and those who love it and see its value. How do we reconcile these three opinions and rewrite legacy code without completely replacing it?
Today we talk with Dave...
Published 09/16/24
One of the reasons why it is difficult to work with legacy code is the lack of preserving the contextual reasons for past coding choices.
Today we talk with Chelsea Troy, a Machine Learning Team Lead at Mozilla and a computer science lecturer at the University of Chicago. She tells us about the...
Published 07/22/24