Comment on The temptation is always there
magic_lobster_party@kbin.social 1 year ago// TODO: Fix later
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.
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.
Later is the name of the intern my company hired when I resigned :)
squaresinger@feddit.de 1 year ago
In a 10 year old commit from someone who’s left the company 5 years ago.
PetDinosaurs@lemmy.world 1 year ago
Bruh. I fixed software from the 90’s.
Scientific software too. Which is way weirder.
decerian@lemmy.world 1 year 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 1 year ago
good question.
Because even trivial things like Fourier transforms (to people like me) are very difficult to understand. 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.
squaresinger@feddit.de 1 year ago
That’s like what happens if From Software made programming challenges.