• Thorry84@feddit.nl
    link
    fedilink
    arrow-up
    0
    ·
    1 day ago

    Hmmm command not found, let me just try the same command a couple more times, this time it will work right?

    In IT teaching users to actually read and understand errors is always an uphill battle.

    • smeg@feddit.uk
      link
      fedilink
      English
      arrow-up
      0
      ·
      13 hours ago

      Never dealt with an intermittent failure or race condition, eh?

    • skulbuny@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 day 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
        0
        ·
        13 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!

        • Trainguyrom@reddthat.com
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 hours ago

          Having written some error messages in a godforsaken database frontend, an error message only means that something didn’t work correctly and may or may not correctly indicate what is actually wrong

        • skulbuny@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          13 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” 😂

          • Ethan@programming.dev
            link
            fedilink
            English
            arrow-up
            0
            ·
            5 hours ago

            I don’t know, have you ever used JavaScript? I’ve run into some really fucking weird bugs. I’ve also spent hours trying to find the source of an error message only to discover the error message was lying and caused by some other error.

      • ugo@feddit.it
        link
        fedilink
        arrow-up
        0
        ·
        1 day 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
        0
        ·
        edit-2
        1 day ago

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

    • kaboom36@ani.social
      link
      fedilink
      arrow-up
      0
      ·
      1 day ago

      Tbh I’d try it multiple times too, just because the concept of cd not being there is horrifying and cannot possibly be the case