• Kissaki@feddit.de
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    11 months ago

    Why are they calling it diff debugging?

    They mention git (and only gitas a tool), so why not call it bisect like git does?

    • canpolat@programming.devOPM
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      11 months ago

      That’s explained at the end (Revisions). Fowler is probably looking for a general term that can be used to describe this specific way of debugging. Since he is aware of git bisect (and I’m sure he knows about hg bisect) there must be a reason he is not preferring “bisect debugging,” for example.

      Edit: The term diff has a clear link with version control. bisect is not that obvious. It may be ambiguous/vague in debugging context. I would still call it “bisect debugging.”

    • Jakub Narębski@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      11 months ago

      Because ultimately you look at the diff of changes, which significantly limits the amount of code you need to examine to find the bug (or at least something that uncovered the bug).