• JoshCodes
    link
    fedilink
    English
    551 year ago

    Run it in your head, find the edge cases yourself, fix the bug… weakling.

    Or do what I do in real life which is patch in new bugs and even a security flaw or two.

  • FuglyDuck
    link
    fedilink
    English
    421 year ago

    the energy of a chaotic neutral?
    “maybe it’ll work, maybe it won’t, but it’ll be FUN”

    or chaotic evil?
    "naw. fuck y’all’s weekend.

    • Psaldorn
      link
      fedilink
      331 year ago

      Merging failing tests so everybody else has failing tests and wastes time figuring out why.

      Nothing neutral here

      • @[email protected]
        link
        fedilink
        11 year ago

        That’s what the pipeline is for. It’s not that hard to pinpoint the commit that lead to the errors.

        • Psaldorn
          link
          fedilink
          81 year ago

          If I rebase my branch with main I do not expect any failing tests. If you waste my time merging shit code, fuck you. Fix your shit.

          Unless prod is on fire and the CEO is prowling (even then, I’d argue standards should be maintained)

          • @[email protected]
            link
            fedilink
            51 year ago

            I don’t say this is good practice, you shouldn’t even be able to merge to main with failing tests. I’ve implemented an emergency flag to do this, but I don’t want to use it in normal, daily business.

  • @[email protected]
    link
    fedilink
    English
    51 year ago

    You can’t trust others to not break your wonderful code. Write tests for the regression.

  • tiredofsametab
    link
    fedilink
    131 year ago

    I physically reacted to this post with a combination of disgust, anger, and fear. Do tests. All of the tests. Randomize the order in which your tests run. Cover all branches.

  • @[email protected]
    link
    fedilink
    211 year ago

    While I know that these days, bugs in code can cause real-world harm (personal info leaks, superannuation records lost, lol google), I find it humorous to think of the equivalent, even worse outcomes in my discipline (chemical/process engineering).

    “Didn’t do any checks, fuck it, I know this calculation is fire 🔥”

    Later: 🔥🔥💥

    • @[email protected]
      link
      fedilink
      51 year ago

      It’s more: I have routed a few pipes in our test system and it’s now spitting out water known to be contaminated but now should have some extra sprinkles in so it’s fine.

      What I’m saying is it’s even worse than didn’t do any checks. It’s willfully ignoring existing checks intentionally.

    • DacoTaco
      link
      fedilink
      12
      edit-2
      1 year ago

      Its funny cause its true. I often design tests to be “if a case/enum value is added this test will explode and tell them to add code here”

  • @[email protected]
    link
    fedilink
    121 year ago

    I get a small amount of joy from clicking the “request changes” button and blocking some doofus from merging lazy untested code.

    • shastaxc
      link
      fedilink
      41 year ago

      I love going into a PR with 3 approvals already and shitting all over it

  • @[email protected]
    link
    fedilink
    11 year ago

    The best way is to try it over and over until it works and then assume it works but then go insane wondering where all the edge case bugs are coming from.

    I wrote a test one time.

  • @[email protected]
    link
    fedilink
    201 year ago

    Oh I trust my code, but I don’t trust my coworkers not to break something on the very next commit.

  • xep
    link
    fedilink
    321 year ago

    Real programmers test in production.