• PunchingWood
      link
      fedilink
      arrow-up
      19
      ·
      1 year ago

      I frequently had to test other developer’s code, the fucking amount of times I heard that shit.

      “Your code ain’t working”

      “It’s working for me”

      “Well it isn’t working for me, did you actually test it”

      “Yes”

      “On anything else than your own PC?”

      “It was working fine for me”

      “It fucking isn’t, look!”

      “…huh”

      For fuck sake just take like 1 minute to press on a frikking button to see if it actually does work.

      Glad I’m not doing that shit anymore.

    • shrugs
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      1 year ago

      That’s why they invented docker

    • 𝚜𝚑𝚊𝚍𝚎𝚊𝚛𝚐
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      Meh. Pedant time.

      The first step of every testcase is supposed to fail to ensure a testing framework can fail in the scope of the testcase. In practice nobody acknowledges this, much less incorporates it.

      Without, one is forced to concede that the test environment is not sane—and, therefore, no case under test is certifiable—because it cannot be known, for certain, if failure was a possibility.

      Nobody cares.

  • DreamButt
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Reminds me of a joke. The purest functional code is the one that never runs

  • BonerMan@ani.socialdeleted by creator
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Its just a syso with Loren ipsum but it generates enough output to blow up your PCs RAM