Re:Poll: In an enterprise, are software clones okay?
by dragonwriter on Sunday April 30, 2017 @02:03AM
(#14230343)
"Clones" are okay when one is the current standard that is used by most of the organization and any others are experiments (possibly in production) for possible future directions of standardization with a clear picture to why you are exploring the alternative, a clear process for evaluating the alternative, and a plan to retire the alternative and put the function back on the standard if the alternative is rejected.
Or if its a separate org that was merged in and hasn't moved on to the standard yet -- and either has a plan to transition or is in the planning process.
Otherwise, no, generally not.
(There are "false clones" that serve the same purpose on a high level description but have clearly delineated different functional roles in the organization -- beyond just "this unit uses X" and "this unit uses Y", but actual different concrete needs that are served, despite being in the same general product category. This can be acceptable with each being standard in its niche, but those niches need to be defined so that the use within the organization doesn't get blurred and you end up with real clones.)
Or if its a separate org that was merged in and hasn't moved on to the standard yet -- and either has a plan to transition or is in the planning process.
Otherwise, no, generally not.
(There are "false clones" that serve the same purpose on a high level description but have clearly delineated different functional roles in the organization -- beyond just "this unit uses X" and "this unit uses Y", but actual different concrete needs that are served, despite being in the same general product category. This can be acceptable with each being standard in its niche, but those niches need to be defined so that the use within the organization doesn't get blurred and you end up with real clones.)