I recently stumbled upon this screenshot while researching social media on the train. Of course, it was followed by a cascade of spiteful comments, criticizing this fresh programmer’s attempt to solve a classical problem in computer science. The modulus operation.
  • merc@sh.itjust.works
    30·
    10 months ago

    I like this bit at the end:

    As a side note, the program is amazingly performant. For small numbers the results are instantaneous and for the large number close to the 2^32 limit the result is still returned in around 10 seconds.

      • merc@sh.itjust.works
        4·
        10 months ago

        For a long time I’ve been of the opinion that you should only ever optimize for the next sucker colleague who might need to read and edit your code. If you ever optimize for speed, it needs to be done with massive benchmarking / profiling support to ensure that the changes you make are worth it. This is especially true with modern compilers / interpreters that try to use clever techniques to optimize your code either on the fly, or before making the executable.

        • Klear@sh.itjust.works
          3·
          10 months ago

          The first rule of optimization: Don’t do it
          The second rule of optimization: Don’t do it yet (experts only)

        • Ephera@lemmy.ml
          1·
          10 months ago

          I’m absolutely on-board …in application code.

          I do feel like it’s good, though, when libraries optimize. Ideally, they don’t have much else to do than one thing really well anyways.

          And with how many libraries modern applications pull in, you do eventually notice whether you’re in the Python ecosystem, where most libraries don’t care, or in the Rust ecosystem, where many libraries definitely overdo it. Because well, they also kind of don’t overdo it, since as a user of the library, you don’t see any of it, except the culmulative performance benefits.

          • merc@sh.itjust.works
            1·
            10 months ago

            Libraries are also written and maintained by humans.

            It’s fine to optimize if you can truly justify it, but that’s going to be even harder in libraries that are going to be used on multiple different architectures, etc.

    • blusterydayve26@midwest.socialEnglish
      51·
      10 months ago

      I’m still mad he didn’t use the size of the number to tell the system which block to read first. I feel like that would be a great use of division or maybe modulus?

  • case_when@feddit.ukEnglish
    29·
    10 months ago

    This is poetry.

    My favourite part is that he uses the modulo operator in his Python script to generate the C code.

  • Hotzilla@sopuli.xyz
    111·
    10 months ago

    Could be easily made 50% space saving by only iffin all odds and return even on else. Maybe one if before to handle overflow to avoid wrong even if over the last if.

    • bjorney@lemmy.ca
      6·
      10 months ago

      Yeah but then ALL even numbers would be slow to compute because you would have to chain through every odd before you know that 2 is even.

      Depends on the expected distribution of input values

  • Great Blue Heron@lemmy.ca
    6·
    10 months ago

    I’m not a good reader - I skim most articles and often miss most of the meaning. I read, and enjoyed, every word of that!

    • Th4tGuyII@kbin.social
      3·
      10 months ago

      There’s not a single thing in this universe that cannot be accomplished with enough IF statements… as long as you’ve got infinite time to wait

      • firecat@kbin.social
        11·
        10 months ago

        The problem with if is the answer comes from user. There’s no mathematical reason or scientific explanation, only programmer who thinks the answer should include the subject.

        • Th4tGuyII@kbin.social
          1·
          10 months ago

          True…

          But even on a more metaphorical level, every single thing that has or will happen in this universe, down to even the smallest quantum fluctuations could be encapsulated into IF statements as long as you had enough of them.

  • Hector_McG@programming.dev
    1·
    10 months ago

    I first saw this joke back in the days of 8-bit home microcomputers. Of course then it only needed 256 lines of code, and took up about 8k of your precious, precious RAM.