Time to run my horrifying python code that builds a bash script that I use to repeatedly call some fortran code and make output I pull back into python for calculating telescope pointings.

My deepest apologies to everyone here who actually has training in making good software. I'm doing science!

(And no, I'm not looking for advice. Hilariously, this dumpster fire of code works well enough, and I don't need to improve it right now.)

@sundogplanets « I’m doing science » « works well enough, don't need to improve it »

With all respect, no, it’s not Science. Your description’s about Engineering, not Science! Nothing wrong with Engineering. For sure it’s required when having scientific activities.

Avoid to confuse one for the other = a great help against https://en.wikipedia.org/wiki/Replication_crisis

It’ll be a better Science if scientific practitioners know the difference between engineering methods and scientific methods. ;-)

Replication crisis - Wikipedia

@zimoun I'm doing engineering in order to make science happen (in this case, point the telescope in the right place on the sky to find the Kuiper Belt Objects we discovered a year ago and measure their orbits, and learn about how the Solar System formed and evolved). How's that?

@sundogplanets « I'm doing engineering in order to make science happen »

I’m totally aligned with this!

And don’t take me wrong, I include myself: we often justify work-enough shortcuts by I’m doing science. It could be understood in two ways: sorry plumbing’s not my business as scientists or I don’t have enough time for plumbing already too busy by “real” science.

Both need to recognize most of our activities as scientists are engineering to make science happens. :-)