551
Any Day Now (sh.itjust.works)
submitted 1 year ago by to c/programmer_humor@programming.dev
48 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 1 year ago (9 children)

Or your employer would invest some money in a proper tool for your job.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 9 child comments
    •
  • [–] 1 point 1 year ago (8 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 3 points 1 year ago (7 children)

    So why haven’t you published the method?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 4 points 1 year ago (6 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 1 year ago (5 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 4 points 1 year ago (4 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 1 year ago (3 children)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 1 year ago (2 children)

    To be very honest, I'm also a tad embarrassed to share my code. I guess I'll ask my professor about this.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •