Ram Ramanathan

Greenhorn
+ Follow
since Apr 15, 2004
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Ram Ramanathan

Let's talk a bit more about Refactoring.However it is defined in theory, when put in practice, especially in a framework based development environment, one better be sure why and how the refactoring has to be done.
The rules governing the refactoring have to be very clearly defined. If a valid refactoring done, I don't see any reason why a class that was thrown out a month ago should ever be reinstated. & refactoring is not just about deprecating classes.It could be deprecating a whole set of artifact(s) in the architectural framework.It could range from modifying the signature of a core component's method to make it more generic & reusable by other functions or moving components between layers(making them more or less shareable).
Such a decision could have refactoring complexities ranging from
a) running a search for all the classes in ur codebase that use this component and just changing the package reference wherever this component is referenced(compile time)
b) Widespread changes to ur code possibly coz some of the classes that were accessing this component before cannot now access it the same way due to component access rules imposed between layers and tiers.
Imagine this happening frequently in an architectural framework used by say 300 developers and if one developer were to unilaterally do such refactoring,it could potentially impact 300 other classes and he may not even be fully aware of the impact, lest he may be doing a partial build.
No matter which CM tool u use, the impact of refactoring has to be very clearly understood by the owners of the architecture/development framework and very strictly controlled. I for one believe that refactoring should never be rampant.