Bringing in New Architecture During Maintenance on Legacy Systems
Posted
by
Mike L.
on Programmers
See other posts from Programmers
or by Mike L.
Published on 2012-06-12T18:02:09Z
Indexed on
2012/06/12
22:47 UTC
Read the original article
Hit count: 277
I have been tasked with adding some new features to a legacy ASP.NET MVC2 project. The codebase is a disaster and I want to write these new features with some thought behind the implementation and not just throw these new features into the mess. I would like to introduce things like dependency injection and the orchestrator pattern; just to the code that I am going to write. I don't have enough time to try to refactor the entire system.
Is it OK to not be consistent with the rest of the codebase and add new features following different design principles? Should I not introduce new patterns and just get the features implemented?
I feel like it might be confusing to the next person to see parts of the system using a design that other parts are not following.
© Programmers or respective owner