358 karma · joined August 30, 2018
The other ways of solving the example of arbitrary heat sources and sinks on a plate range from hacky combinations of simpler methods, to tedious math, to complicated general methods. If you switch from heat to pressure distribution, you'd have the same types of options, but the specific methods would be different.
In my anecdotal experience, the problem is that many programmers just don't like working to a spec.
I also appreciated the consistent URL scheme because it let me easily scrape all the PDFs to read them offline. The one bummer is that the links at the end of the PDF versions seem to be broken now.
https://www.analog.com/media/en/selection-guides/Equation_Pu...
I agree that a hazard analysis should have identified it. But whether it did or didn't, there are still many possible reasons why it wasn't addressed effectively. Hence, a systemic failure.
I have no idea if it's legal, but any punishment would probably be on the company rather than the individuals.
It also takes money. But why bother protecting the consumer or even the company if you're not legally or financially liable yourself?
There's little incentive to do things right. And when there is, most people will only ever learn the hard way.
Curious what the better way to swap implementations would be?
For testing and simulation, it's a way to mock dependencies. You get to test the otherwise exact binary you'll deploy. And you can inject tracing and logging.
Solver installations tend to be long-lived, but require customizations, upgrades, and fixes over time. Dynamic linking lets you do that without going through the pain of reinstalling it every time. Also with solvers you're likely to see unconventional stuff for performance or even just due to age.