That's wild, I have worked on large scientific software, coupled with electron microscopes (off all kind of types, bio, material, big, small) and we had over 700 types of processings of different data and visualisation. Without OOP in there it would have been a one man orchestra-mess per client.

We had those people clinging to their scripts too, they were actually the best getting the results out from bad aquisitions, but it's kind of complicated because it's not the scripts that are important but the dude using them.

The OOP was good because it tied it all together (you could easily string compute modules together to form new treatments of data for example), that's not needed in a small, one-situation setup, but still I'd code something to manage it all if I were you (and had the possibility to do so ofc), maybe your gui does that. But then again, I don't know how it all works where you work so what do I know 🤷🏻‍♀️.

Cheers

[–] mnemonicmonkeys@sh.itjust.works 1 points 18 hours ago (1 children)

still I'd code something to manage it all if I were you (and had the possibility to do so ofc)

You're continuing the exact problem I described. Quit. Dictating. To. Me. How. My. Code. Should. Work.

"Best practice" is a fucking guideline. You can't bilndly apply it to every single situation and expect it to work all the time. There's always exceptions and nuance that must be accounted for, and the people that refuse to ackowledge that are fools.

Go find someone else to gaslught, jackass.

[–] Valmond@lemmy.world 1 points 7 hours ago

And your code is unmaintainable, has no unit tests and needs someone with the mindset of a 15 yo to "fix it" all the time, or so it seems.

Good luck learning to code for real with that mindset.