Why is refactoring important? Do you know this? Your code works, but after a few months nobody understands it anymore - not even you. This is where refactoring comes into play: it improves readability and maintainability without changing the functionality. What is refactoring? Refactoring refers to changes to the code that
Clean code on a greenfield site is easy. Or not. But clean code in legacy code is definitely not easy. If the code has grown over years or decades, the many violations of the clean code principles cannot simply be eliminated by various refactorings. The one reason is
Refactorings are an integral part of our developer life. It would be nice to always be able to start from scratch, implement new features and realize new ideas. However, we are much more frequently confronted with having to readjust existing source code. In this context, refactorings play a crucial role, especially when we are working on legacy code.
Exploring the code vastness of the legacy space - Where no test has gone before In the galaxies of software development, ensuring quality is of paramount importance and yet so often neglected. Working in untested and unknown code is as common as it is universally disliked. Who looks forward to
At the HerbstCampus 2016 in Nuremberg I gave a talk on refactoring C# legacy code. You can find the video of the talk here.
In this video, I explain the Mikado method, which can be used to break down complex refactorings into small steps.
When it comes to legacy code, many developers feel uneasy. Starting a project "on a greenfield site" is much more fun than being in the swamp of the "brownfield"
When it comes to legacy code, many developers feel uneasy. Starting a project "on a greenfield site" is much more fun than being in the swamp of the "brownfield"
CCD Academy GmbH
Am Steinernen Kreuz 27
53343 Wachtberg
English 
German