Once you understand engineering, transferring that skill to another engineering discipline is not that hard.
For example, the equations for Newtonian mechanics, electronics, beam design, rotating inertia, etc., are interchangeable.
> his competence to build orbital data centers
Since nobody has yet built an orbital data center, nobody is competent at it yet.
It might have been medium difficult back in 1985, but the state of the art has progressed in the intervening 40 years. The constraint of correctness makes things trickier because it further imposes three requirements: completeness, uniqueness, and determinism.
Unless the implementer has the skill to prove these properties about the algorithm they've implemented, such an implementation is likely not to achieve those requirements.
I also implemented IEEE 754 floating point in asm. For that I did have an exhaustive test suite, and passed it 100%.
(Though, Steele-White expresses these slightly differently, as preserving information, having the shortest possible output, and rounding correctly. Completeness, uniqueness, and determinism seem to be equivalent and are easier to prove.)
--
0: Available at <https://fmt.dev/papers/Dragonbox.pdf>. It's pretty easy to understand either with a numerical analysis background or after having worked through volume 2 of Knuth's TAoCP.
And why are CEOs as smart as engineers now.
This isn't Twitter. You don't have to suck up to him. He won't ever see this.