In the old system, I could just punch in the code or scan the QR code, but now I have to do this dance of “why won’t it connect?” every time
Having drivers reach for their phone when they're approaching traffic lights - common pedestrian crossing points - is categorically moronic.
Then later on one of the doctors asked J&J if a test for cyanide is done for each batch in QA at the factory. J&J said yes, each batch was tested for the presence of cyanide.
The doctor then asked, "Why were they testing for it(cyanide)?", kinda blew my mind. Implying that J&J knew cyanide contamination was a possibility at the factory itself.
I have not been able to read the docs fully, but some questions:
* How do you handle state that is too big to send to the client fully? In a chat application, does the client need to have the whole channel history, or is syncing a subset of that supported? * Does permissioning support partial CoValues? For example, "You can edit the contents but not the title of the 'blog post #11' object" * Do you have resources about the suggested data modelling? Things like how granular should a CoValue be and what the trade-offs are. * How do you handle deletion? Do you tombstone? Is there a way to fully scrub a value from history (to support, for example, GDPR's right to erasure)?
However, a shooting is just one type of mass casualty event.
It looks like there’s 3 hospitals within 15 minutes of the Las Vegas strip, I’m curious if there’s any attempt to allocate patients equally so that no single hospital becomes overwhelemed.