• Droggelbecher@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    9 hours ago

    Nobody has built a tool that executes a mathematical method that I have developed or at least adapted, at least not before I publish the method.

      • Droggelbecher@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        5 hours ago

        Because I’m in academia and it’s a slow process to get things published in a way that ‘counts’ to the university and scientific community. I often need to implement stuff first to check a few things, whether it’s viable etc.

        • marsza@lemmy.cafe
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 hours ago

          That’s not how it works. Put it on GitHub like the rest of us and stop making excuses.

          • Droggelbecher@lemmy.world
            link
            fedilink
            arrow-up
            3
            ·
            5 hours ago

            I’m sorry to tell you this but people do not, in fact, publish mathematical proofs on GitHub routinely. You publish them on arxive once the paper is done. And then in a journal. The solvers themselves aren’t even what it’s about at all, they’re just to do numerical experiments with to have some examples. They aren’t immediately useful for any applications outside niche research.

            • marsza@lemmy.cafe
              link
              fedilink
              English
              arrow-up
              1
              ·
              5 hours ago

              You’re right that mathematical proofs are usually published on arXiv and then in journals. But since you mentioned code: sharing code on GitHub is actually very normal in research. Even if it’s just a solver or scripts for experiments, putting it on GitHub helps with reproducibility, gives others a chance to learn from or build on your work, and makes it easy to cite. There’s no obligation to polish it perfectly—lots of research repos are just “as is” snapshots to support a paper.

                • marsza@lemmy.cafe
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  5 hours ago

                  Now, that is completely understandable. This is also a reason I don’t publish most of my things. They work, they work well, but… Some of it is kind of nasty. However, other developers are going to understand. Just mention this in the read me file. Or better yet, use this as an opportunity to refactor code. An LLM could be very helpful For that process.

                  If you are not familiar with the process of using git or GitHub, i’m sure many of us, including myself, would be more than happy to help you.