• JoshCodes@programming.devEnglish
    2 years

    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@lemmy.worldEnglish
    2 years

    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@lemmy.world
      2 years

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

      Nothing neutral here

      • jaybone@lemmy.world
        2 years

        I haven’t played DnD in like 20 years. Is “Chaotic Dickhead” an alignment now?

      • RamblingPanda@lemmynsfw.com
        2 years

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

        • Psaldorn@lemmy.world
          2 years

          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)

          • RamblingPanda@lemmynsfw.com
            2 years

            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.

  • RagingRobot@lemmy.world
    2 years

    Tests are just booby traps for the other engineers so they don’t break your code by mistake.

  • MisterFrog@lemmy.world
    2 years

    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: 🔥🔥💥

    • mitchty@lemmy.sdf.org
      2 years

      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.

  • Phen@lemmy.eco.br
    2 years

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

  • jjjalljs@ttrpg.network
    2 years

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

    • shastaxc@lemm.ee
      2 years

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

  • tiredofsametab@fedia.io
    2 years

    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.

        • tiredofsametab@fedia.io
          2 years

          People can pull <table> from my cold, dead hands.

          (though I’m usually only using it to display some status just for me and not for external consumption; the UI side can have a JSON if it ever comes to that).

          I used to be a full-stack dev, but I’ve been pure backend for so long now, everything I knew is outdated or deprecated.

      • hollyberries@programming.dev
        2 years

        Tbh I’m not a web person (more of a backend person) and don’t know the recommended practices. display: grid; is a good friend of mine xD

        • Kissaki@programming.devEnglish
          2 years

          I think using display: grid; as your default is the better default, so you’re all set. :)

  • whotookkarl@lemmy.world
    2 years

    Weak code lacks tests

    Alt: if strength relies on unity I need to switch to game dev

  • velvetThunder@lemmy.zipEnglish
    2 years

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

  • PenisDuckCuck9001@lemmynsfw.comdeleted by creator
    2 years

    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.