Re:How to Read Other People's Code -- And Why
by olliesaunders on Friday October 23, 2009 @04:16AM
(#898448)
Michael Feathers' Working Effectively with Legacy Code is the authority on this, I think.
[ Parent
| on HN ]
Re:How to Read Other People's Code -- And Why
by silentbicycle on Friday October 23, 2009 @08:35AM
(#898629)
Not quite - it's primarily focused on safely retrofitting unit testing onto legacy codebases, since restructuring code to make it testable can easily break it.
His definition of legacy code is code that doesn't have tests, so you can't fix it or replace units of it without unknowingly introducing bugs.