Software-Engineering

There is a particular kind of hubris that shows up in engineering projects. It is the moment you look at 87 Fortran files representing forty years of accumulated ocean physics and think: I can do this in Python. Not translate the interface. Not wrap the binary. Rewrite it. Subroutine by subroutine, comment by comment, constant by constant, until what you have is a Python package that produces the same numbers — to a scientifically meaningful degree of precision — as a compiled Fortran model that has been validated against field observations across four decades. ...

Most engineers doing single-phase convection calculations pick one correlation and move on. Usually Dittus-Boelter, because it’s in every textbook and everyone knows it. Sometimes Gnielinski, if they’re careful. Rarely anything else. I understood why. You’re not writing a dissertation on Nusselt number correlations — you’re sizing a heat exchanger or checking a thermal margin. The correlation is a means to an end. But that habit started bothering me. Not because Dittus-Boelter is wrong — it isn’t, within its range — but because the choice is invisible. It’s not documented. It’s not justified. And when conditions change (higher Reynolds number, different fluid, different geometry), the engineer who comes next has no idea why that correlation was used in the first place, or whether it’s still appropriate. ...