“Good code should be resilient to bugs. It should make it easier to do the changes that you want to the system. Some refactoring could make it harder to make changes. So, if you guess wrongly the direction of the software, then it can have a negative effect."
Christian Clausen is a Technical Agile Coach specializing in teaching teams on how to refactor their code properly. He is also the author of “Five Lines of Code”. In this episode, Christian explained in-depth about refactoring, when and how we should do refactoring, the components, workflow, and pillars of refactoring. Christian also shared about a few important architectural refactoring, such as composition over inheritance and changing by addition instead of modification. Finally, Christian also shared a few tips for writing quality software, such as the five lines of code rule, the habit of deleting code, and avoiding optimization and generality.
Listen out for:
_____
Christian Clausen’s Bio
Christian Clausen works as a Technical Agile Coach teaching teams how to properly refactor their code. He has previously worked as a software engineer on the Coccinelle semantic patching project, an automated refactoring tool. He holds an MSc degree in Computer Science and has taught software quality at a university level for five years.
Follow Christian:
Our Sponsor
Are you looking for a new cool swag?
Tech Lead Journal now offers you some swags that you can purchase online.
These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available.
Check out all the cool swags by visiting https://techleadjournal.dev/shop.
Like this episode?
Subscribe on your favorite podcast app and submit your feedback.
Follow @techleadjournal on LinkedIn, Twitter, and Instagram.
Pledge your support by becoming a patron.
For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/56.