93 karma · joined June 9, 2017
I know this because I worked as an ML engineer at an extremely successful company that automated medical coding using deep learning.
The confusion stems from conflating a "perfect solution" with a "human augmented" one.
90% of coding cases are trivial, have low value and can be done by a model. 10% are really subtle and need human expertise.
That's fine. You can make a billion dollar company on low hanging fruit. I think it's best not to conflate the perfect solution with a very good solution.
Original software for it is a bit hard to work with, improvements in https://github.com/ongdexter/ar3_core
I would caution against using nan to always mean infeasible. Instead users should catch experiments outside the feasibility region and return a special infeasible value. This will increase visibility into the behavior of the optimizer, because it leaves nan to be used for values inside the region of constraint that are still problematic (due to bugs, numerical instability, etc)
Robots are very hard, and Boston Dynamics has been around for almost 40 years and still isn't anywhere close to making a lot of money.
Apps have added a lot more value to my life than BD ever has.
Fwiw I interviewed with BD a few years ago, and am focusing on robotics, so I'd like the opposite to be true
Fwiw I'm a Canadian that just signed a Google offer to work out of downtown SF because I hate the winter too. I think people care more or less about the weather based on their hobbies / interests.
So the interface between the engineers and the people is not to find solutions together, or to find flaws together, but for engineers to find solutions and flaws, and the people to pick the one that they are happiest with.
(I'm not certain my understanding of the quote is right, just sharing my interpretation / an alternative to the ones you shared)