• e0qdk@kbin.social
    link
    fedilink
    arrow-up
    113
    ·
    1 year ago

    Rule 9 from Agans’s Debugging: If you didn’t fix it, it ain’t fixed

    Intermittent problems are the worst…

    • marcos@lemmy.world
      link
      fedilink
      arrow-up
      34
      ·
      1 year ago

      The problem is, how do you fix it if you can’t make it break?

      The worst thing is when somebody comes to you saying “yeah, I had this problem yesterday, but it’s working now”.

      • Neshura@bookwormstory.social
        link
        fedilink
        English
        arrow-up
        22
        ·
        1 year ago

        this is a case for excessive logging man

        likely won’t help you actually fix the issue because miraculously you didn’t log the three variables you actually need but it’ll make you feel better in the meantime

        • kameecoding@lemmy.world
          link
          fedilink
          arrow-up
          8
          ·
          edit-2
          1 year ago

          and gives you some headroom in improving performance since it’s being choked by the excessive logging

        • folkrav@lemmy.world
          link
          fedilink
          arrow-up
          6
          ·
          1 year ago

          Fully agree, but they’re usually kind of annoying to track regardless. On the opposite side, sometimes even getting it to trigger on purpose to be able to add a regression test can be pretty tricky, depending on the cause. Timing or time/date based stuff is a common culprit…

          • ryannathans@aussie.zone
            link
            fedilink
            arrow-up
            5
            ·
            edit-2
            1 year ago

            Don’t tell me about time and date, I am still recovering from some moron that used datetime.now() for some unit test data setup and sometimes two records (which needed to have the same time) had very slightly varying time which caused all sorts of intermittent test failures that were very tricky to nail down. Database triggers were failing causing failures in all sorts of tests in a random fashion

  • DraughtGlobe@feddit.nl
    link
    fedilink
    arrow-up
    72
    ·
    1 year ago

    ngl my programming career helped me stay grounded in reality. Every impossible issue turned out to always have a cause, a reason to be there. Could have taken weeks to track down the issue, but there was always a cause.

    But still… every 3 or so years… something actually impossible pops-up. Impossible to fix, impossible to reproduce, and suddenly gone from existence, as if it was never there.

  • saltnotsugar@lemm.ee
    link
    fedilink
    English
    arrow-up
    36
    ·
    1 year ago

    The longer I’m in IT, the more I realize that the adeptus mechanicus might be on to something with beseeching the machine spirit.

    • peopleproblems@lemmy.world
      link
      fedilink
      arrow-up
      29
      ·
      1 year ago

      A lot of people think I’m joking when I say I’m a good at what I do because I’m a witch doctor with computers. Software Engineering requires experience with the occult, at a minimum.

      • saltnotsugar@lemm.ee
        link
        fedilink
        English
        arrow-up
        27
        ·
        1 year ago

        “In my professional opinion, this network is haunted.”
        …haunted?
        (Points to various certifications) “HAUNTED.”

          • The Gay Tramp@lemmy.ca
            link
            fedilink
            English
            arrow-up
            5
            ·
            1 year ago

            The demons are attracted to doorways, passages between spaces, worlds, and realms. And printers are the ultimate doorway: a portal through which ideas and concepts can leave the software realm and enter the physical

      • Floey@lemm.ee
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        In effect, we conjure the spirits of the computer with our spells.

        • The Gay Tramp@lemmy.ca
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          I actually had a concept for a fantasy world, where magicians craft spells much the same way software devs do. So you make your spell and publish it to the ether, and then anyone can invoke it using the magic word (package name), assuming the have the right dependencies available (eye of newt or whatever). But spells might have bugs. So if you used eye of red newt while the spell smith built it with the expectation you had eye of blue newt you might get unintended consequences

          • Swedneck@discuss.tchncs.de
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            i mean it’s pretty common for runes to just be conceptual programming languages and if you do something wrong then instead of having a lighter you get a bomb

  • Traegs@lemmy.world
    link
    fedilink
    arrow-up
    32
    ·
    1 year ago

    The other day I launched an old game and got met with an error, something about directX9 and missing a redistributable file or something. Decided not to fuck with it.

    Yesterday I launched it again to take a closer look at the error message to see if I could fix it. No error message, game booted without issues.

    My confusion.

  • MisterD@lemmy.ca
    link
    fedilink
    arrow-up
    24
    ·
    1 year ago

    I have this issue once in a while with PowerShell.

    The environment gets f’up as you develop. You get strange shit happening or it blows up.

    Restart PowerShell or reboot and it’s all good

  • Oodelallic@lemmy.ca
    link
    fedilink
    arrow-up
    21
    ·
    1 year ago

    lucky, you have code gnomes. leave out an offering of mountain dew and pizza rolls to appease the spirits.

  • takeda@lemmy.world
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    1 year ago

    Still better than my Go experience 2 years ago.

    • fails when deployed, after adding debug statements looks like in one structure there’s 2 instead of 1, and looking at the code that should be impossible. Issue happens every single time.
    • the same exact unmodified container when downloaded and run locally works correctly every time.
  • LazaroFilm@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    1 year ago

    I had that happen with embedded programming when you forget to flush the eeprom after changing your saved values.

    • Neshura@bookwormstory.social
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      hmm embedded. Beautifuly memories from uni. One lab my team forgot to remove a register whose supposed purpose was only enabling a communications bus (documentation didn’t mention it doing anything else). Turns out that same register disables the dac which we needed for the new excersise. You learn to love the hardware datasheets real quick.

      • LazaroFilm@lemmy.world
        link
        fedilink
        English
        arrow-up
        10
        ·
        1 year ago

        And when the data sheet is wrong that gets fun. You start parsing I2S for each bit and record the result until you see a pattern. Or when your program crashes the USB and you can’t reupload without hitting boot or reset but they are inside the box.

        • Tolookah@discuss.tchncs.de
          link
          fedilink
          arrow-up
          7
          ·
          1 year ago

          MY PEOPLE!!! My code recently decided to not erase the flash when writing new firmware, bricking the device. Good times. (Old code || new code does not make for a working system)

          • LazaroFilm@lemmy.world
            link
            fedilink
            English
            arrow-up
            5
            ·
            1 year ago

            I’m dealing with this right now. Making the largest embedded project for me (self taught) RP2040 in Cpp with a TFT touch screen, an IMU with fusion, a strip of “neopixels”, a 12v battery voltage reader, some Lemo connectors and custom cables, all in a 3D printed case in 3 parts. I’m so close to the end but still facing some code issues.

            • Tolookah@discuss.tchncs.de
              link
              fedilink
              arrow-up
              3
              ·
              1 year ago

              Pixels are wonderful, but such a perilous path…

              Start playing with a pixel, then get a board with WLED set up, then start running xlights on a beaglebone to synchronize several instances, for holiday lighting. Suddenly there’s several hundred leds in the front yard

              • LazaroFilm@lemmy.world
                link
                fedilink
                English
                arrow-up
                3
                ·
                1 year ago

                Haha! I feel you. Luckily my project only involves about 20 pixels on a high density strip (332pixels/m) to be used as a small 1D display.

      • LazaroFilm@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 year ago

        On small computers like Arduino there is a very small memory called eeprom that stays when powered off. It saves ultra low level data (at the bit and byte level) if you don’t “format” after changing what is being saved where it then tries to read gibberish and things go bonk.

  • FruitfullyYours@lemmy.world
    link
    fedilink
    arrow-up
    12
    ·
    1 year ago

    I’ve recently had the opposite: code worked then the next day without anything changing it didn’t.

    Turned out the J-Link programmer always needs the license check to work, but that expires every day at midnight. It only prompts again if you choose the app and restart it. So I couldn’t get my debugger to work and spent hours trying to figure it out until I did the best thing. I turned it off and on again.

  • Tabugti@feddit.de
    link
    fedilink
    arrow-up
    12
    ·
    1 year ago

    In university, we had to complete weekly tasks. A few times, the validation script provided by my professor returned an error, meaning that my solution had a mistake. When I tried rerunning the script the following day, my answer was accepted. At the end of the last lecture, my professor came to me and told me that I was usually the first one to hand in a solution and that he sometimes used my answers to validate his results.