3 ms·
I've been in a situation where I've had to regularly maintain the "new" and "old" codebase. It's not sustainable. The problem is that such a situation quickly
by gwbas1c 10y ago
I've been in a situation where I've had to regularly maintain the "new" and "old" codebase. It's not sustainable.
The problem is that such a situation quickly devolves into a scenario where porting changes between the two versions of the product takes a sizable development effort. Once v2 has 2-3 major refactors, merging a change in v1 means that the change essentially has to be completely re-implemented for v2.
What causes this? Basically, management thinks that "new" is just a feature bolted onto "old;" or management wants to "have its cake and eat it too." Resolving this situation requires careful planning and communication early in the project stage, before creating "new."
- What are the features that can be made in isolation from "old" code, so that merging changes into "old" doesn't create lots of merge conflicts?
- When is the point where we can freeze "old," so that major refactoring can happen on "new?"
- What is the soonest we can move users onto "new," even if it means that we don't build all the features we need?
- What parts of "new" really should be build on "old," or, what refactoring should be done on "old," so we can avoid branching issues?