A picture of Edsger Dijkstra with a concerned face and the following text on top: How software engineers look at your code when you solve the problem using two tables — instead of using the Maxwell-Ross-Karmakar algorithm, which is marginally optimal in ordered sets bijectable to the exponential curve
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 months ago* (1 child)

the hang up for me is more the not caring about time to compute

aeroish is my experience, and for me those have all cared about time to compute

generally that’s one of the biggest constraints to the point of being super strict

like major money being spent on modeled approximations and processing speed costs eclipsing pretty much everything on the design side

tables for weather, angles, altitude, position this would be tiny compared to some we’re using

30 year old equipment is even more taxed given the likely feature creep in my experience

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 months ago

    I'm guessing you were doing in flight aero stuff? I've been more in the medical and manufacturing space but the aero I did we were doing post-flight processing for reports. We had almost no memory to operate on, probably because of all the tables you're referencing that others were using.

  • source
  • parent