By piccoloprincipe
via css.dzone.com
Published: Jan 23 2012 / 17:11
In the scenario of today, a subclass and superclass are not very different: the evolution of the code has brought them to this situation. Behavior has been removed, or moved elsewhere in the system, and they are almost the same entity.
The Collapse Hierarchy refactoring provides a series of steps to unify two such classes into one, simplifying the design.
-
Test-Driving Development for the Firefox OS Phone
-
5 Tips for Mainframe Modernization: Transitioning to a GUI
-
Dealing with Windows Azure Storage transient faults
-
Why Plug-and-Use Desktop BI Software Is So Powerful?
-
No-nonsense plain English introduction to ESB and SOA
-
Strategies for Scaling Agile Software Development
Add your comment
