Abstract
Most of the guidance applies to smaller chunks of code and decisions implemented in hours or days, not weeks or months. There were a great book on architecture scale refactoring with distilled wisdom and case studies of successes and failures. This article only touches on that but it covers some topics that augment the good advice you will find in Martin Fovvler's Refactoring book and Michael Feathers' Working Effectively with Legacy Code.
Full Text 
Sign-in/Register to access full text options
Sign-in/Register to access full text options 
Paper version not known
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
