[cl3misch]

Nicely put, thank you. What can sadly be even worse are physicists-turned-coders who think code is good if 1. everything is encapsulated as much as possible and 2. there are comments for every line.

Of course, I once was that physicist! Now I prefer working with arrays and functions that receive arrays and return arrays, even in the top-level, user-facing script.

But who knows, maybe there will be a next stage in the journey!

[montecarl]

> there are comments for every line.

I used to work at a company that wrote an atomic scale simulation package. Every dev was a physics/chemistry PhD turned coder. We didn't quite hit one comment for _every_ line of code, but we were close! At first I really hated this style; one comment every few lines. However, I eventually learned to kind of like it, even though it was a bit redundant.

I don't really have a point here, but I just wanted to echo your statement that the physicists-turned-coder style is real!

[geysersam]

Jesus living through that now. Physics PhDs and postdocs turned coders all around. They dislike anything "not made here" and can build tools for years before a prototype solution to the actual problem exists. System design decisions are made frivolously and end user feedback is actively discouraged, "have to be careful who we show this to" one said in a meeting after something got criticized by an end user representative. I'm venting a bit but it is a culture clash for sure.

[StarlaAtNight]

Jesus is back?!? And she’s a Physics PhD?!?