Because based on “asked it to make a profit” I expect financials in the story. Even if it is a bit of a ”Clarkson’s Bot”, for the farm there is discussion of the numbers.
CSS does suck because of the globals. Class names, ids, z index values are all areas where one commonly bumps into other developers in sometimes confusing ways.
But to the point of the article, it’s a technology one has to learn. There are name spacing solutions in css (layers) and around css (css modules, panda, tailwind, etc).
I think another challenge folks may have with CSS is thinking visually. It’s not automatic. In art school one learns both how to see and how to render, and generally learning how to see clearly is a bigger challenge than learning how to render.
First off, he had discomfort with the study methodology. Didn't go into details, but was surprised that the FDA was less conservative than himself in this case.
Secondly, it has been common in his practice for someone to have an unusual event. Someone does something out of the ordinary, they have an unusual circumstances, they don't adjust their treatment, and something goes wrong.
His question was -- does the device have a reset button? Is there a way to restart the management and learning? The answer is no -- the device will learn! But there's no way for the patient or the physician to adjust the treatment. So his answer is -- he would never recommend this device, not the way it's currently setup. It's opaque and there's no means for a person to influence the device's learning.
Once I lived in an apartment with a safe that had been locked open. It was a giant, heavy thing too large to move. The owners simply renovated the apartment around it.
Eventually I got bored and started playing with it. Since it was locked open, it was possible to start taking apart the door from the inside. Once the tumblers were exposed, I figured out the combination.
It was tremendous fun!
If anyone here is in a similar situation, I recommend cracking the safe. Building the robot seems like a nice bit of mechanical engineering:
- write a sax event based parser that scaled but was low level
- use a DOM parser with a fairly convoluted API. The combination of attributes and children makes for wordy accessors.
Both YAML and JSON provide formats that more readily deserialize into native map / list / string / number types which at the time was quite convenient.