SE-Radio Episode 295: Michael Feathers on Legacy Code

Defining Legacy

Michael Feathers explores the concept of legacy code, emphasizing that it often implies age and inheritance rather than quality. He notes that the term can evoke fear among developers, as it is associated with outdated or problematic systems. Felienne Hermans adds that most codebases are considered legacy due to their inherent complexity and constraints.

It's like, oh, that's legacy. I'm a little bit scared of it. I don't want to touch it, that kind of thing.

--- Michael Feathers

Despite this perception, Michael acknowledges that there are high-quality legacy systems, particularly in regulated industries, where rigorous standards are maintained 1 2.

   

Greenfield vs. Legacy

The contrast between legacy and greenfield projects reveals distinct challenges and opportunities. Michael Feathers argues that while greenfield projects offer the freedom to innovate, they quickly accumulate legacy aspects as they grow. He suggests that working with legacy code can enhance a developer's skills, making them more adept at managing greenfield projects.

Working legacy code is great training for being able to create better greenfield applications.

--- Michael Feathers

Felienne Hermans concurs, noting that both project types require a deep understanding of code and the ability to adapt to evolving challenges 3 4.

   

Perception Impact

The perception of legacy code in the industry often impacts developer motivation and practices. Michael Feathers describes a common bias where legacy projects are seen as less prestigious compared to greenfield ones. He emphasizes the importance of recognizing the value in maintaining and improving existing systems.

People do start new projects all the time...but the bulk of the work out there is an existing code basis.

--- Michael Feathers

Felienne Hermans highlights that understanding legacy code is crucial for long-term software sustainability and innovation 1 2.