this post was submitted on 24 Oct 2025
201 points (98.6% liked)
Programmer Humor
27127 readers
2758 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Like I said, the problem with OOP advocates is that most of them are calling for bolts to be destroyed in this analogy. If they weren't so fanatical about it we wouldn't be havining this conversation.
It's not a random example. I can't go into detail, but it's the code I work on on a daily basis. It's a physics model for industrial equipment. Highly customizable for customers, and I need to know exactly where various sub assemblies are located and be able to move them in various configurations.
And scripts doesn't "fix" the problem. It's more that using functions is infeasible due to the difficulty in cramming everything into input arrays, so scripts end up being orders of magnitude more efficient to work with. The scripts are all called from a function, which does allow us to interface with other groups or our own custom GUI.
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
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.
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.