And somehow every single time the problem was so easy to solve, but apparently crying about it is the better solution.

  • Psaldorn
    link
    fedilink
    648 days ago

    So many times I see junior Devs (or not so juniors) and normies seeing an error message and, visibly, static plays between their ears on their mental TV set, then they just click the first button that looks appropriate and complain it didn’t work.

    The text of the message does not get read or parsed.

    “You need to close the program to continue”. Doesn’t work.

    “Unexpected X at line N” Doesn’t work.

    Drives me insane.

    • @JcbAzPx@lemmy.world
      link
      fedilink
      English
      117 days ago

      Unfortunately, so many error messages are so utterly useless that it has taught many people that all errors are just pointless background noise even if they’re actually giving useful info.

      • Psaldorn
        link
        fedilink
        117 days ago

        I mean, java and Microsoft errors are preceded by 120 characters of useless trash oftentimes, that is equally as infuriating.

        • @Cenzorrll@lemmy.world
          link
          fedilink
          37 days ago

          Or Windows gives you a blue screen and just “BAD_POOL_HEADER”.

          I got that intermittently at work on an instrument about every week or two. The best answer I could find was “it could be software or hardware related”. Yeah, thanks for that, problem solved. Wish I had thought of that. Not even a time stamp. Finally found out when it occurred to within 20 minutes and there was jack shit in the logs.

          IT ended up calling in a service tech to re-image the computer.

          • Psaldorn
            link
            fedilink
            27 days ago

            Ah, windows logs, another amazing experience that doesn’t make me want to kill everyone.

            tail /var/log/thing.log is far too easy