[Acknowledgements: This post was originally created by Shawn Morrison, who danced onto another project and passed this along to me to edit and make my own.  Thanks, Shawn.]   In his book “Working Effectively with Legacy Code,” Michael Feathers states, “Legacy code is code without unit tests.” I believe this is a helpful way of […]

Legacy code is code without unit tests. Michael Feathers, Working Effectively with Legacy Code I think that Michael Feathers’ definition of legacy code (which is almost always synonymous with technical debt) is one of the most concise and useful definitions I have come across. Getting a handle on technical debt and wrangling legacy code is one of […]