What’s esoteric about Rusts syntax? I can’t relate at all, but maybe I had just the right background of languages commin into Rust.
Comment on Which programming language is hard to understand?
ComradeWeebelo@lemm.ee 1 year ago
I find syntax wise, Rust is very closely bordering on esoteric. My employer is currently considering switching to Rust and I can say working in a department with a bunch of Data Scientists with varying degrees of programming experience and capability, this switch, if it happens, will probably be poorly received.
zygo_histo_morpheus@programming.dev 1 year ago
thisisnotgoingwell@programming.dev 1 year ago
Bruh on one post people are bandwagoning rust and then on another post people calling it esoteric 🤣 hard to see what’s what past the hype. I mostly code in Python though so I might need to find out for myself
Potatos_are_not_friends@lemmy.world 1 year ago
Prayers man.
We brought in a dept of data scientists when we bought a company.
I never witnessed the worse code ever.
I don’t know if they were all 1y bootcamp grads or something. I thought math formulas was supposed to be elegant. But everything was written top-down, no reusability, like coding excel formulas that feed one cell into another and takes a hour or two to calculate. I nope’d so fast out of one “system” they built which was just daisychaining SQL queries into a new file that is fed into another SQL query repeat 7 times.
0xc0ba17@sh.itjust.works 1 year ago
Mathematicians and scientists are notoriously awful programmers. They get shit done but with absolutely 0 regard to good practices and reusability.
coloredgrayscale@programming.dev 1 year ago
Would have thought mathematicians would be slightly better at writing functions
UFODivebomb@programming.dev 1 year ago
I’ve experienced similar.
One thing that helped: separating research code from production.
Research is to answer a decision problem and much of that optimization problems that are in software engineering do not, and should not, apply.
Once the research problem is answered. Reproducing that answer with production quality systems should be it’s own project. This also serves as a reproduction of the science in the research. Satisfying that hallmark of the scientific method.
Course, getting a company to agree to such an arrangement is near impossible. Especially if they have never been crippled by the mismatch expectations of putting research code in production.
As that is an organizational problem not just an engineering problem, good luck convincing management.
An alternative, if I can’t get such an arrangement is the building a platform that supports integration of research code. That can be… uh… hard. Aside from the people challenges not all tech can support such a platform.