• GreyEyedGhost@piefed.ca
    link
    fedilink
    English
    arrow-up
    12
    ·
    22 hours ago

    The way I heard it, and think sounds better, is below.

    99 little bugs in the code,

    99 bugs in the code.

    Fix one bug, compile it again,

    101 little bugs in the code.

    For a more modern version, you could go with

    Send it to Claude, compile it again,

    1001 little bugs in the code.

    • PhoenixDog@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      3 hours ago

      Why would you use ‘again’ in any version of this when the third line is supposed to rhyme(ish).

      It’s “Take one down, patch it around”

    • Focal@pawb.social
      link
      fedilink
      arrow-up
      6
      ·
      20 hours ago

      Close to the one I heard as well

      99 issues with bugs in the code

      99 issues with bugs

      You take one down, ya patch it around

      You got 105 issues with bugs in the code

  • BigDanishGuy@sh.itjust.works
    link
    fedilink
    arrow-up
    21
    arrow-down
    1
    ·
    1 day ago

    My neck hurts from just looking at that setup.

    This may just be my age showing, but unless you’re stuck writing .net, or maybe java, then there’s no reason to have more than 120chars of horizontal real-estate in your IDE. Get a 16:10 monitor and flip it 90° instead.

    Also who codes like that in a professional context? How do you read your notepad, when all you have is some christmas ornamentation for lighting? Again it may be an age thing, but often I rely more on my pencil and notepad than my mouse.

    • mkwt@lemmy.world
      link
      fedilink
      arrow-up
      9
      ·
      1 day ago

      I don’t understand why people go to wide formatting. If you stick to 80 columns, you can fit like 4 different files side by side at the same time on today’s monitors. No more flipping back and forth!

      • heartSagan5@lemmy.zip
        link
        fedilink
        arrow-up
        1
        ·
        1 day ago

        Because Windows. Also, you gotta flip back and forth to hide your entertainment, like a nudey mag in a comic book.

    • mlg@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 day ago

      You don’t understand, its clearly the workstation of an MSFT engineer who needs to 50 nested deep entries of XML lol.

    • egrets@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      23 hours ago

      Agreed, I could never order my punch cards with lighting like this. I’m also unsure how the keyboard and mouse are working without the PS/2 jack and cable, and those potted plants aren’t anything like the Devonian flora I’m familiar with.

        • GreenKnight23@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          24 hours ago

          the neck pain alone would negate any boost to productivity.

          I just use a standing desk with a 4k 70" screen. I have all the width and height I’ll ever need with proper text scaling.

          • hikaru755@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            6 hours ago

            the neck pain

            …your 70" screen is higher than even a regular 32" 16:10 monitor is wide, so yours would actually be worse in terms of neck pain.

            So sure, your setup might still be superior, but using neck pain as the argument is just, no.

            • GreenKnight23@lemmy.world
              link
              fedilink
              arrow-up
              1
              ·
              4 hours ago

              it’s a standing desk. the screen is mounted from the ceiling and is a perfect 1:1 with my field of vision.

              then when I want to sit, my chair reclines back and my positioning is similar to this.

              1000004916

              I have macros to switch DPI so it’s easy to swap back and forth.

              it’s very comfortable. since I used to spend 12-18 hours a day online it had to be.

      • egrets@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        23 hours ago

        I’ve never bought into the “top of the monitor should be at eye level” stuff that DSE guidance teaches. I reckon for a single screen, my eyes should be level with the top third of the screen – so I don’t have to crane my neck, but I’m also not encouraged to hunch over.

      • Noxy@pawb.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        20 hours ago

        don’t you lose rven faintly ergonomic access to your input devices if you stand up tho?

  • Blow_Me@midwest.social
    link
    fedilink
    English
    arrow-up
    3
    ·
    23 hours ago

    The phonetics or w/e of the lyrics lining up is doing something itchy to my brain.

    Proposed improvement:

     

    99 bugs in the code on the wall,

    99 bugs in the code.

    Take one down,

    patch it around,

    1456 bugs in the code on the wall!

  • SeductiveTortoise@piefed.social
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 day ago

    Me, trying to fix failing tests my colleagues keep ignoring.

    “48 of 1307 fail, but for these seven it’s this’d the assertion expecting a new enum value, easy!”

    “106 of 1307 fail. What the fuck?”

      • SeductiveTortoise@piefed.social
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 day ago

        Their solution was to remove them from the pipeline. And I wondered why test coverage went down in SonarQube.

        0.9% is not a lot of coverage, let me tell you that.

        • ulterno@programming.dev
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 day ago

          So I was given a project after a major part of it was made by an AI fanatic coworker and right before delivery, we were asked to make some specific types of documentation to submit.
          One of which included code coverage reports.

          The party receiving the documentation then said that they need 100% test coverage…
          Of a GUI application that interfaces with multiple proprietary devices over serial port, network, USB etc and is dependent upon the physical environment to get all code paths.

          I just gave that all to the AI fanatic coworker and am not even planning on reading the test code.
          If the program itself satisfies my logical requirements, I’ll ask him to change the test code to match the changed application code.

            • ulterno@programming.dev
              link
              fedilink
              English
              arrow-up
              1
              ·
              4 hours ago

              Whenever I have something to doubt, I make a test executable.
              But for GUI stuff, it has mostly been manually verified tests and not really in the tests configuration of cmake.

              I have seen automated GUI tests of Okular and I don’t want to have to implement them myself on a project that will have someone randomly ask during the acceptance procedure to change how a feature works.

              • SeductiveTortoise@piefed.social
                link
                fedilink
                English
                arrow-up
                1
                ·
                3 hours ago

                I prefer a mixture. I think automated tests are extremely helpful. But you should also use the application and create a test protocol you can follow again and again.

  • limer@lemmy.ml
    link
    fedilink
    arrow-up
    5
    ·
    1 day ago

    Jokes like this will never be not funny; and it boosted my confidence today ( seriously) as I find a difficult bug of my own.

    Honestly, about my own bug; I don’t see why scrambled data is so bad. Keeps users on their toes, and avoids them becoming too complacent

  • we is doomed!@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    22 hours ago

    As a little segue, is this the best way to organize 2x 34" monitors, I’d thought to go side by side but have no idea.

    • NuanceDemon@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      1
      ·
      22 hours ago

      Vertically oriented (portrait) screen(s) go to the side.

      Two ultrawides next to each other involves two things that eventually get annoying:

      • lot of head turning, fine at first but ends up achey
      • your keyboard is either centred on one screen, or centred on neither, and at some point you’ll always end up twisted - typing in one direction and looking in another.

      Neither seemed like a big deal to me at first but it seems like most people end up at vertical stacking.

      Also it uses way less desk space.