Felienne talks with Michael Feathers about Legacy Code. When is something legacy? Is working on legacy different from working on greenfield code? Do developers need different skills and techniques? Testing legacy code. How to test a legacy system? When do we have enough tests to feel safe to start coding? Techniques to make legacy systems more testable.
SE Radio 295: Michael Feathers on Legacy Code
Join the discussion
You must be logged in to post a comment.
5 comments
More from this show
Vinay Tripathi, a senior network engineer in Google Backbone Engineering and an 18-year network engineering veteran, discusses BGP...
Tim McNamara, a well-known Rust educator, author of Rust in Action (Manning), and a recipient of a Rust Foundation Fellowship in 2023...
Simon Wijckmans, founder of c/side — a company that focuses on monitoring, securing, and optimizing third-party JavaScript —...
“Working Effectively with Legacy Code” one of the best book ever!
Awesome podcast. Very useful insight on maintaining and enhancing legacy code easily by adding tests. Thanks Michael for sharing your ideas and SE radio for organizing this event.
I always struggle with Michael’s definition of legacy code – code without tests. It seems there should be a different name for that concept.
Then again, “legacy” would be somewhat arbitrary… code you just wrote yesterday? Code written by someone else? How long ago?
I really like Michael’s statement that creating many tiny things means “the complexity moves into the wiring”. It’s difficult/impossible to understand the flow of modern OOP applications… but easier to change and test.
Really liked this one, very useful. Thanks. The radio host was good as well.
[…] that are related are good enough that it is definitely worth giving a listen to. Maybe start with Episode 295 where Michael Feathers talk about Legacy codes. Each of their episodes is about an hour […]