Thank you for the explanation!
That is pretty interesting, and a whole lot different from building
consumer software. I spend a lot of my time thinking about reliability
of systems, but usually at a higher level -- I assume that systems will
fail, so I (try to) design architectures around those failures. What if
I lose X or Y, what happens?
It sounds like you have to go a lot lower level and verify everything.
(An endless task?) I suppose some of it gets rolled up -- i.e., you
don't have to worry about, say, motor burnout specifically, but more
just "there is a 0.01% cumulative chance of failure for every 1 hour of
usage" and that includes physical wear and tear, unexpected failures,
If you are unable to use this captcha for any reason, please contact us by email at email@example.com