• @NocturnalMorning@lemmy.world
    link
    fedilink
    211 months ago

    Sure, refactoring is sometimes necessary. But refactoring also introduces new bugs often. Our code base is constantly being refactoring, and it’s not more reliable, stuff is constantly breaking.

    • magic_lobster_party
      link
      fedilink
      411 months ago

      Refactoring for the sake of refactoring is rarely a good thing. It should be done with a clear purpose in mind.

      • @NocturnalMorning@lemmy.world
        link
        fedilink
        -311 months ago

        Why are programmers so arrogant? They do have unit tests, and a dedicated test team. Refactoring can and does introduce bugs. It’s a fact.

        • @luciferofastora@lemmy.zip
          link
          fedilink
          211 months ago

          How solid is the unit test coverage? What about regression tests? If you get new bugs creeping in all the time, your bug-catchers aren’t doing their job

        • @MyNameIsRichard@lemmy.ml
          cake
          link
          fedilink
          311 months ago

          Frankly, if your test suite isn’t catching 95% or more of the bugs, there’s a problem with the test suite and if uat aren’t catching 95% or more of the remainder, there’s a problem with uat