• skulbuny@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    21
    ·
    18 hours ago

    I learned early in my software engineering career these two beautiful rules of debugging:

    1. Read all of the words
    2. Believe them
    • smeg@feddit.uk
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      Addendum to 2: never believe that what they say is relevant to what’s actually happening here. You have a lot of faith that the people writing error messages knew what they were doing!

      • skulbuny@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        2 hours ago

        I mean, if the error says “variable foo is not defined” I don’t think it’s wise to go “I’m pretty sure it’s defined, the compiler is just wrong” 😂

    • ugo@feddit.it
      link
      fedilink
      arrow-up
      6
      ·
      14 hours ago

      Until you write a compiler error in some deeply templated C++ code, in which case just reading every word takes all day

      /s but not too much

    • elvith@feddit.org
      link
      fedilink
      arrow-up
      9
      ·
      edit-2
      17 hours ago

      Unless you were the one writing the program and its error messages - then check, that you didn’t mess up there…