• raman_klogius@ani.socialEnglish
    19·
    1 day ago

    I don’t understand these kinds of people. Do the text recognition part of their brain completely shuts down when their eyes look at a warning/error message? Like do they only see amorphous blobs in place of the warning/error message?

    • Rayquetzalcoatl@lemmy.worldEnglish
      3·
      14 hours ago

      I’ve worked with developers like this in the past. They’ll see an error come up, read it, and then sort of just start clicking on random stuff and refreshing the page. Eventually, you roll over and say “Hey man, how’s dev going?” And they may or may not say “hmm, got this error…”, at which point you enter into the most frustrating partner programming session of your life, because they won’t stop scrolling and clicking when you’re trying to read the god damn error message on their screen

    • UntouchedWagons@lemmy.caEnglish
      3·
      1 day ago

      Sometimes (not in this instance) the error message is completely worthless. I remember one time trying to configure automatic backups in Cloud Native Postgres and it just wasn’t working, the errors were opaque. So I asked on the project’s github what the problem was and the devs were quite unhelpful. Some random user came along and said “Oh you need to set the S3 region like this…” and backups started working.

  • count_dongulus@lemmy.world
    1412·
    2 days ago

    My #1 pet peeve is when someone comes to me with a problem, and the solution is in the fucking console output or error message.

    On a bad day, if I had unilateral power, I would fire those people on the spot.

    • GiveOver@feddit.uk
      17·
      2 days ago

      Error message: “you must manually run ‘sudo dpkg --configure -a’ to fix this”

      Junior dev: 😵

    • jjjalljs@ttrpg.network
      105·
      2 days ago

      At one of my old jobs, we had a suite of browser tests that would run on PR. It’d stand up the application, open headless chrome, and click through stuff. This was the final end-to-end test suite to make sure that yes, you can still log in and everything plays nicely together.

      Developers were constantly pinging slack about “why is this test broken??”. Most of the time, the error message would be like “Never found an element matching css selector #whatever” or “Element with css selector #loading-spinner never went away”. There’d be screenshots and logs, and usually when you’d look you’d see like the loading spinner was stuck, and the client had gotten a 400 back from the server because someone broke something.

      We put a giant red box on the CI/CD page explaining what to do. Where to read the traces, reminding them there’s a screenshot, etc. Still got questions.

      I put a giant ascii cat in the test output, right before the error trace, with instructions in a word bubble. People would ping me, “why is this test broken?”. I’d say “What did the cat say?” They’d say “What cat?” And I’d know they hadn’t even looked at the error message.

      There’s a kind of learned helplessness with some developers and tests. It’s weird.

      • quoll@lemmy.sdf.org
        17·
        2 days ago

        i think that guy works for us now :D

        the best bit is he pings multiple senior devs in slack separately.

        so we are all wasting our time doing the same shit in parallel for the same muppet.

      • MelodiousFunk@slrpnk.net
        37·
        2 days ago

        There’s a kind of learned helplessness with some developers and tests. It’s weird.

        I got handed the keys to the network monitoring suite many moons ago. I immediately started editing the default alert actions to display relevant information, and in some outlier cases escalation procedures.

        Most times, it was ignored. Other times, it was skimmed and half-followed. A few people outright refused to do anything differently than they had before (kick it up the ladder).

        Glad to be rid of that place.

    • hemko@lemmy.dbzer0.comEnglish
      45·
      2 days ago

      Same here. For some fucking reason reading is so damn difficult

      Error: pull your head out of your ass

      Hey I got this error what do

    • lmmarsano@lemmynsfw.comEnglish
      21·
      2 days ago

      The selective illiteracy gets me: clearly, they can read each other’s messages. The text in an error message? Brain shuts off.

      • chicken@lemmy.dbzer0.com
        9·
        2 days ago

        tbf the text in error messages very often leads down a rabbit hole of barely relevant context, rather than to the shortest path to getting things to work as you expect them to. Or maybe they just don’t understand what the word “deprecated” means or implies.

        • hemko@lemmy.dbzer0.comEnglish
          1·
          12 hours ago

          OTOH you learn a lot while in that rabbit hole, making the next time you research something a little bit easier.

          • chicken@lemmy.dbzer0.com
            1·
            2 hours ago

            Well sometimes. Learning what deprecated means would probably have very broad usefulness. Learning the ins and outs of the library codebase that generated that error when you’re only going to make minor use of it once might not. There’s a practically infinite amount of things to learn and we all have finite time, attention, and space in our heads.

    • Nat (she/they)@lemmy.blahaj.zone
      26·
      2 days ago

      Minecraft mod users are the worst. They’ll post a screenshot of a version mismatch or dependency error that literally tells them how to resolve it and ask “hey, this mod isn’t working, how do I fix it?”

        • skulblaka@sh.itjust.works
          20·
          2 days ago

          I figured that shit out when I was 12 and there were way less learning resources about it on the internet then. Fuck 'em. Someone who never has to solve their own problems without handholding is someone who will never learn to solve problems, period. IPad kids are scared of error messages and that’s their problem. They’ve never had to troubleshoot anything before.

          Though I can’t blame the kids entirely. Most error messages in the modern era absolutely suck nuts. Half of them nowadays (at least on the client side) are just

          “oopsie, there’s been a widdle fucky wucky, sooorrrrryyyyy 💖”

          With zero actionable info in it. Not even a distinction of You/We/Your ISP Has Fucked Something Up. I guess they figured (correctly) that the end user wasn’t going to read it anyway so why bother, but this drives me nuts when I see it.

    • Serinus@lemmy.world
      6·
      2 days ago

      Sometimes I’ll copy paste the error message back to them. Apparently it works better when it’s in a text message.

    • mmddmm@lemm.ee
      2·
      2 days ago

      On the context of a node package, I’m pretty sure that “solution” is utterly worthless and doesn’t come even close to targeting the same functionality the old code had.

      But odds are the one place the library author used that function can be replaced by a completely different functionality that happens to use the suggestion.

      • deadbeef79000@lemmy.nz
        7·
        2 days ago

        On the context of a node package,

        It’s probably a package with one five line function, and a poor implementation at that.

  • i_stole_ur_taco@lemmy.ca
    906·
    2 days ago

    People like this are the reason AI is so unreliable at exploring code issues.

    Like, I just want Copilot to look at my dependencies to explain a vague error I’m seeing and it’s telling me to downgrade Ruby, upgrade Rails, and install Python. Bro, it’s a node package.

    • Ashelyn@lemmy.blahaj.zone
      201·
      2 days ago

      Maybe the onus should be on LLM developers to filter out trash like this from their training datasets

      At any rate, it’s extremely unhelpful to not include a version number at the very very least

      • Boomkop3@reddthat.com
        6·
        2 days ago

        Damn, if only you could learn to understand the errors. Then you woudln’t have to depend on an llm with hundreds of underpaid workers behind it.

        git gud

        • Ashelyn@lemmy.blahaj.zone
          3·
          2 days ago

          Me? Reading that there’s a drop-in replacement function for the one that was deprecated, in the error message? Why I’d never!

          • Boomkop3@reddthat.com
            1·
            1 day ago

            Hold up, hold up… We’ve got an ai to do the reading for us. I’ve asked it to summarise what you said. That should give me a bit less reading to do…

            The statement appears to be a sarcastic or humorous remark expressing frustration or disbelief regarding an error message that includes a “drop-in replacement function” for a deprecated function. The speaker seems to imply that it is frustrating or almost unbelievable to encounter a message that offers a solution, particularly one suggesting that the replacement can seamlessly take the place of the deprecated function.

            By saying, “Why I’d never!”, the speaker is likely exaggerating their frustration or mock surprise, indicating that they might have encountered this situation often or that such suggestions are generally not taken seriously.

            This type of comment suggests that the speaker might be somewhat jaded or irritated by encountering such “helpful” messages, perhaps due to previous experiences where the suggested solutions were inadequate, difficult to implement, or not as straightforward as they seem.

            “Right? It’s almost like they think a one-line replacement function is going to fix all the issues. It’s never as simple as the message makes it sound, is it? I’ve definitely been burned by those before.”

            This response acknowledges the speaker’s frustration and shares a similar sentiment, while also reinforcing the idea that these “helpful” messages don’t always live up to expectations.

  • Lazycog@sopuli.xyz
    99·
    2 days ago

    Well, atleast they explained how they “fixed” the problem.

    Got to love those “all good, problem solved/went away” - posted 5 years ago

    • notabot@lemm.ee
      20·
      2 days ago

      How do such people program?

      They don’t. They used to copy and paste stuff they found on the internet, then when it doesn’t work they made a barely coherent post on Stack Exchange, or maybe the issue tracker of one of the packages they think they’re using. I suppose that nowadays they copy and paste whatever they get out of the LLM de jour, then try to tell it that it didn’t work, copy and paste the answer and repeat until it either compiles or they finally give up and post to an issue tracker.

    • floofloof@lemmy.ca
      21·
      2 days ago

      I have a bunch of colleagues like this. If they were left to their ways we’d still be using unpatched frameworks from 20 years ago. I find it pretty frustrating.

      • PattyMcB@lemmy.world
        27·
        2 days ago

        Same. “If the warning doesn’t break the build, just ignore it,” (even if it literally says it’s going to break the build in the next major release)

        • JordanZ@lemmy.world
          8·
          2 days ago

          Bold of you to assume they’ll update to the next major release. Attempts update, breaks the build…rollback! We’re locking the release to this specific version now.

          I have lived this comment and the fix was like updating a few dependencies and some configs…it took ten minutes. They were on some deprecated version for years…

          Edit cause typo/autocorrect