Comment on What are your strategies for diving into a large, complex codebase?Comments−yawz12yMichael Feathers' "Working Effectively with Legacy Code" is a great book that I would recommend for such situations.−InformalReliefOP12yLooks interesting. Is this useful if you work with relatively new code (no Cobol lurking in dark corners)?−shoo12yIn the book, Feathers defines legacy code as code without tests.So it's not really about old languages or old code. It's pretty easy to write (or inherit) new, difficult to test code, with no tests, in whatever language you please.−osivertsson12yThis really is an excellent book! It has helped me keep my sanity when working on large legacy codebases. Highly recommended.
Comments
Michael Feathers' "Working Effectively with Legacy Code" is a great book that I would recommend for such situations.
Looks interesting. Is this useful if you work with relatively new code (no Cobol lurking in dark corners)?
In the book, Feathers defines legacy code as code without tests.
So it's not really about old languages or old code. It's pretty easy to write (or inherit) new, difficult to test code, with no tests, in whatever language you please.
This really is an excellent book! It has helped me keep my sanity when working on large legacy codebases. Highly recommended.