It often takes a while for the probes to stablise and get an accurate reading, so this is a very common pattern, but I haven't looked into why. I think part of it may be the machine calibrating to the flow of blood through the area of skin you have chosen. You often apply the probe and sit it there for 30-60s waiting for it to stabilise.
If you are worried, ask them to leave it on throughout your consult. You should see it sit at 99-100% for the rest of your stay.
That single person you are paying a sub-par wage won't be providing 24/7/365 support, which is a big benefit of AWS / cloud providers. It's also a bit of insurance on your hardware in case of failures, free replacement. Finally, if something catastrophic was to happen, with a recent-ish offsite backup it's usually pretty trivial to setup on a different region or even cloud provider. With your own hardware, that's a bit harder.
I agree though with one of the parents, AWS costs here can likely be significantly reduced. I cut costs in half by (a) reserving instances and (b) thinking about EBS and downgrading / downsizing where possible rather than using the defaults.
With no backup? What if you suffer a massive head trauma (or an unfortunate death), no way to recover your millions of dollars for friends and relatives? I'm guessing people put this stuff in their wills these days, how secure is a will?
Depends on the application obviously. A lot of social groups would likely be meeting once a week. It's just a simple example though of how the step function could be useful.
For your example, you would just need a step with some kind of range. So you could say step=7, range=5 to allow them to pick from the first 5 days of every 7 (or to get trick step=7 range=-2 to eliminate the last 2 days). I'd hazard a guess they thought about this kind of stuff, but realised it would be complicated pretty quickly.
If something runs weekly (e.g., every Saturday), it could be useful to verify the user has picked a Saturday. Not sure if the dropdown would grey out other days too, as that could be useful to be able to remove unavailable days.
Raises an interesting point regarding a staking strategy. Given the bookmakers are going to cut you off, it potentially could be better to just go as hard as you can & live with the risk.
Alternatively, an interesting tweak would be to see what the best historical edge has been, and wait for the best opportunities to surface & only bet on those. Effectively you limit yourself by saying "I can only place N bets per bookmaker, what should my strategy be?"
I think it's more so there is a chance to come out ahead. E.g., everyone sitting on a pokie machine absolutely knows in the long run, the casino wins out. However they are hoping they are the 1/million that gets the jackpot and "beats" it. The same reason people buy lottery tickets I guess.
Other people simply like the social aspect of a lot of games (craps, poker, blackjack, roulette) and the excitement/thrill of seeing some big winners. You know in the long run you are losing X%, but still go to burn hours and have some fun.
They really should have automated the bet placement from the outset, which would have made it worth the effort. Could probably make a few thousand $ before getting cut off, per person. Definitely a worthwhile venture, considering you could probably then sell off the software after using it for some more profits.
It would be interesting to see where they are making their edge. I wouldn't be surprised if it's on a lot of these minor leagues with more uncertainty, as opposed to stuff like the EPL
If you are worried, ask them to leave it on throughout your consult. You should see it sit at 99-100% for the rest of your stay.