• ImplyingImplications@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      YanDev is a literal pedophile. It’s honestly mind boggling people care more about a guy who won’t sign a petition on preserving video games than pedophiles and bigots. I don’t get the hate.

      • deur@feddit.nl
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        Because this dumbass has existed for a lot longer than the single moment you are using to construct the strawman of “the enraged internet user over nothing other than a ‘petition’ (HUGE mischaracterization, he’s not eligible to sign in anyway)” and just like when yanderedev was finally widely controversial, the “yanderedev code is bad lol” memes and jokes were very popular.

        Can you at least pretend you understand how “the continuous flow of time works” before you post the dumbest shit ever?

      • shea@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        it’s not that he “wont sign it”. lmao. its that he comoketely unprovoked started a hate campaign against it, literally on the spot hearing about it on stream, directed his viewers not to engage with the petition and started making up a bunch of reasons while talking in that confident-but-clulesss voice about how its destructive and awful and short sighted, making up a bunch of atuff about it that was immediately disproven, just spewing all this vitriol for no reason. Not engaging with it is one thing but actively fighting against a wonderul consumer rights campaign like this, not to mention how important iy is to gaming history to be able to preserve games, is so anti-gamer i dont understand how he ever got a following. Hes a dipsh who talks out of his butthole and he appeals to the kind of lobenly nerd that thinks being an asshole is cool

  • QuazarOmega@lemy.lol
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    No, no, you should group the return false lines together 😤😤

    if (number == 1) return false;
    else if (number == 3) return false;
    else if (number == 5) return false;
    //...
    else if (number == 2) return true;
    else if (number == 4) return true;
    //...
    
  • 4am@lemmy.zip
    link
    fedilink
    arrow-up
    0
    ·
    5 months ago

    Fucking rent free. Jesus Christ you clowns, I almost want them to take away all your video games now

    • Ambii [she/her]@hexbear.net
      link
      fedilink
      English
      arrow-up
      0
      ·
      5 months ago

      oh no not my toys, like all good consoomers i put 99% of my self worth and identity into the things i consume mindlessly so this is devastating.

      • 4am@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        I think you got wooshed here

        The guy in the picture is PirateSoftware, accused of sabotaging the Stop Killing Games initiative in the EU.

        This post is part of a coordinated harassment campaign by big angy gamers because bad nerd man say companies won’t listen to their little lib demands to the EU

        So instead of regrouping their efforts (which, I might add, they did, and they got their day in parliament) they (started off by) basically trashing this dude until he lost a large portion of his community. Because like they didn’t like how he defended his position. About video games. And now the fucking internet won’t shut up about it even though they got their way again through toxic bullying. And it annoys me. So I shitpost about it wherever I can because I hope it annoys them too.

        • Oriel Jutty :hhHHHAAAH:@infosec.exchange
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          There’s a lot of distorted facts here, but the weirdest one to me is “instead of regrouping their efforts (which, I might add, they did, and they got their day in parliament)”. The first half just contradicts itself (“instead of doing X, which they did, …”???) and the second half (“they got their day in parliament”) is verifiably, obviously false: The EU petition is still ongoing and collecting signatures. The deadline is July 31.

      • 4am@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        I’ve never met anyone cool who cooks up strawmen memes because they’re exhausted all their actual criticisms.

        The piratesoftware shit is so tiresome. Who the fuck cares? What is this going to accomplish? He’s not even popular anymore

        • TrickDacy@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          Who cares? You. You’re the one who knows what this even is. ReNt FrEe is always a sign of having no argument

    • normalexit@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      TDD has cycles of red, green, refactor. This has neither been refactored nor tested. You can tell by the duplication and the fact that it can’t pass all test cases.

      If this looks like TDD to you, I’m sorry that is your experience. Good results with TDD are not guaranteed, you still have to be a strong developer and think through the solution.

      • FishFace@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        As the existing reply stated, there are only ever finitely many tests.

        My issue with TDD is that it pretends to drive the final implementation with tests, but what is really driving the implementation is the monkey at the keyboard thinking, “testing for evenness should be done with the modulo operation,” not exhaustive tests.

        • normalexit@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          The monkey at the keyboard thinking is what software development is. When faced with a failing test, you make it pass as simply as possible, and then you summon all your computer science / programming experience to refactor the code into something more elegant and maintainable.

          In this case that is using math to check if the input is divisible by two without a remainder. If you don’t know how that works, you’re going to have a bad time, like the picture in this post.

          TDD doesn’t promise to drive the final implementation at the unit level, but it does document how the class under test behaves and how to use it.

          • FishFace@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            5 months ago

            When faced with a failing test, you make it pass as simply as possible, and then you summon all your computer science / programming experience to refactor the code into something more elegant and maintainable.

            Why bother making it pass “as simply as possible” instead of summoning all that experience to write something that don’t know is stupid?

            TDD doesn’t promise to drive the final implementation at the unit level

            What exactly does it drive, then? Apart from writing more test code than application code, with attendant burdens when refactoring or making other changes.

            • normalexit@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              5 months ago

              The rhythm of TDD is to first write a failing test. That starts driving the design of your production code. To do that you need to invoke a function/method with arguments that responds with an expected answer.

              At that point you’ve started naming things, designing the interface of the unit being tested, and you’ve provided at least one example.

              Let’s say you need a method like isEven(int number): Boolean. I’d start with asserting 2 is even in my first test case.

              To pass that, I can jump to number % 2 == 0. Or, I can just return true. Either way gets me to a passing test, but I prefer the latter because it enables me to write another failing test.

              Now I am forced to write a test for odd input, so I assert 3 is not even. This test fails, because it currently just returns true. Now I must implement a solution that handles even and odd inputs correctly; I know modulus is the answer, so I use it now. Now both tests pass.

              Then I think about other interesting cases: 0, negative ints, integer max/min, etc. I write tests for each of them, the modulus operator holds up. Great. Any refactoring to do? Nope. It’s a one-liner.

              The whole process for this function would only add a few minutes of development, since the implementation is trivial. The test runtime should take milliseconds or less, and now there is documentation for the next developer that comes along. They can see what I considered (and what I didn’t), and how to use it.

              Tests should make changing your system easier and safer, if they don’t it is typically a sign things are being tested at the wrong level. That’s outside the scope of this lemmy interaction.

              • FishFace@lemmy.world
                link
                fedilink
                arrow-up
                0
                ·
                5 months ago

                Either way gets me to a passing test, but I prefer the latter because it enables me to write another failing test.

                But you could just write that failing test up front. TDD encourages you to pretend to know less than you do (you know that testing evenness requires more than one test, and you know the implementation requires more than some if-statements), but no-one has ever made a convincing argument to me that you get anything out of this pretence.

                Tests should make changing your system easier and safer, if they don’t it is typically a sign things are being tested at the wrong level

                TDD is about writing (a lot of) unit tests, which are at a low-level. Because they are a low-level design-tool, they test the low-level design. Any non-trivial change affects the low-level design of a component, because changes tend to affect code at a certain level and most of those below it to some degree.

        • normalexit@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          In a world where this needs to be solved with TDD there are a few approaches.

          If you were pair programming, your pair could always create a new failing test with the current implementation.

          Realistically I would want tests for the interesting cases like zero, positive even, negative even, and the odds.

          Another approach would be property based testing. One could create sequence generators that randomly generate even or odd numbers and tests the function with those known sequences. I don’t typically use this approach, but it would be a good fit here.

          Really in pair programming, your pair would get sick of your crap if you were writing code like this, remind you of all the work you need to get done this week, and you’d end up using modulus and move on quickly.

          • Oriel Jutty :hhHHHAAAH:@infosec.exchange
            link
            fedilink
            arrow-up
            0
            ·
            5 months ago

            If you were pair programming, your pair could always create a new failing test with the current implementation.

            But I’m not pair programming. And you can’t always create a new failing test because int is a finite type. There are only about 4 billion cases to handle.

            Which might take a while to type up manually, but that’s why we have meta-programming: Code that generates code. (In C++ you could even use templates, but you might run into compiler recursion limits.)

            More to the point, the risk with TDD is that all development is driven by failing test cases, so a naive approach will end up “overfitting”, producing exactly the code required to make a particular set of tests pass and nothing more. “It can’t pass all test cases”? It doesn’t have to. For TDD, it only needs to pass the tests that have actually been written. You can’t test all combinations of all inputs.

            (Also, if you changed this function to use modulus, it would handle more cases than before, which is a change in behavior. You’re not supposed to do that when refactoring; refactoring should preserve semantics.)

            • normalexit@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              edit-2
              5 months ago

              Read the article about property based testing. It is the middle ground between what you are describing and practicality.

              I often pair with myself, which sounds silly but you can write failing tests by yourself, it just isn’t as fun.

    • FrederikNJS@lemmy.zip
      link
      fedilink
      arrow-up
      0
      ·
      5 months ago

      Unittest in Python, enjoy! If you pass it with a function like the one in OPs picture, you have earned it.

      import unittest
      import random
      
      class TestOddEven(unittest.TestCase):
          def test_is_odd(self):
              for _ in range(100):
                  num = random.randint(0, 2**64 - 1)
      
                  odd_num = num | 1
                  even_num = num >> 1 << 1
      
                  self.assertTrue(is_odd(odd_num))
                  self.assertFalse(is_odd(even_num))
      
          def test_is_even(self):
              for _ in range(100):
                  num = random.randint(0, 2**64 - 1)
      
                  odd_num = num | 1
                  even_num = num >> 1 << 1
      
                  self.assertTrue(is_even(even_num))
                  self.assertFalse(is_even(odd_num))
      
      if __name__ == '__main__':
          unittest.main()
      
      • FishFace@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        I don’t want unseeded randomness in my tests, ever.

        Seed the tests, and making these pass would be trivial.

          • FishFace@lemmy.world
            link
            fedilink
            arrow-up
            0
            ·
            5 months ago

            The right tool here is tests at a level higher than machine code instructions that have been in CPUs since the 70s. Maybe TDD practice is not to test at this level, but every example of TDD sure tends to be something similar!

    • Destide@feddit.ukOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      5 months ago

      As we’re posting examples I’ll add how lovely it is in Elixir. Elixir def not putting the fun in programmer memes do. One reason I picked it because I can’t be trusted to not be the meme.

      def is_even?(n) do
        rem(n, 2) == 0
      end
      
      • balsoft@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        5 months ago

        I mean, it would be almost this exact thing in almost any language.

        fn is_even(n: i64) -> bool {
            n % 2 == 0
        }
        
        even n = n `rem` 2 == 0
        
        def is_even(n):
            return n % 2 == 0
        

        etc

        • vinnymac@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          Personal preference, but elixir just strikes a balance that doesn’t make me feel like I’m reading hieroglyphs so I’m actually happy to see it praised.

          • fushuan [he/him]@piefed.blahaj.zone
            link
            fedilink
            English
            arrow-up
            0
            ·
            5 months ago

            I would have preferred for the function to be called mod, since it’s the modulo operation, which in math is represented with a percentage or “mod”. Most programming languages use a percentage because of that, so do a lot of calculators.

          • balsoft@lemmy.ml
            link
            fedilink
            arrow-up
            0
            ·
            5 months ago

            Yeah, I agree that Elixir is a fine language for some tasks. I personally find the readability somewhat average, but it’s very maintainable (due to how it enables clear program structure), the error handling is great, and the lightweight process system is amazing.

  • huf [he/him]@hexbear.net
    link
    fedilink
    English
    arrow-up
    0
    ·
    5 months ago

    pff, i aint reading all that, lemme optimize it:

    private bool isEven(int number) {
        return rand() < 0.5;
    }