• @[email protected]
    link
    fedilink
    31 year ago

    That’s intentional. So if one part of the code suffers a random mutation and spontaneously develops a bug, the redundant code can still ensure the proper functioning of the program while the bug gets fixed.

    Just take care if you merge two branches that contain the same bug; you might end up with a program without functional redundant code. That’s why you should never merge closely related branches.

    • @[email protected]
      link
      fedilink
      11 year ago

      It’s how isoforms functions with different signatures evolve. As long as it isn’t harmful it tends to stick around. Then the different code may develop adaptations which fit it into a niche if it is a selective advantage for the organism code base.

  • DonjonMaister
    link
    21 year ago

    Applying the (DRY) Do Repeat Yourself principle.

  • Gresham Law
    link
    fedilink
    1
    edit-2
    1 year ago

    Depends on what you are developing & the language used but a simpler codebase is the definition of security/privacy by design that’s how you get more power.