• Square Singer
      link
      fedilink
      229 months ago

      In a 10 year old commit from someone who’s left the company 5 years ago.

        • @decerian@lemmy.world
          link
          fedilink
          59 months ago

          Why is that weirder? The people writing scientific software are, by and large, less good at writing software than people who only specialize in software development. I’d expect there to tons of terrible engineering practices in an old code base like that

          • @PetDinosaurs@lemmy.world
            link
            fedilink
            5
            edit-2
            9 months ago

            good question.

            Because even trivial things like Fourier transforms (to people like me) are very difficult to understand to those that don’t know them. They took me years to understand. Non scientific software engineers do not understand those. It’s just a different course of education.

            You’re also right about old code base as well. Algorithms like these belong in c++ (or C or fortran), and it’s extremely difficult to explain why to people who have no understanding of numerical computing.

            It’s just different education.

        • Square Singer
          link
          fedilink
          19 months ago

          That’s like what happens if From Software made programming challenges.

    • @rodolfo@lemmy.world
      link
      fedilink
      29 months ago

      I wish I was so lucky to have comments.

      in real life, I’m fighting with - I’m not joking - a few dozen “quick patches”. code does not reflect in any point functional requirements, and dude is adamant he’s in the right and supersarcastic in any occasion.

      • @PetDinosaurs@lemmy.world
        link
        fedilink
        39 months ago

        I’ve been working at my current company for almost a year.

        I had no idea it could be this bad.

        I actually had to fight/plead with someone to “please read the code”. Guy did get fired though.