I had a scary experience in a Model S on auto-pilot going over a bridge where the car swerved left and almost hit the concrete barrier. Not entirely sure what happened but since then, I've been hesitant to use auto-pilot 100% of the time.
Why would you use it at all at that point? If this guy took his experience with autopilot the first time it almost crashed his car, he'd probably still be alive.
I would try to set up Remote Desktop. It is amazing how nice it is to have high powered computation available on a light weight, long battery life machine. Simply VPN / VNC in, and you are set to go. Also, iOS 13 supports any Bluetooth mouse, so that may help as well.
>a lot of different industries and company sizes with the goal to automate pretty much any business process.
I'm going to take a different approach. Your audience so broad that you don't know who your real customers will be. From all those "industries", you need to pick one that will be the money maker and slowly expand to other ones.
Um. Do you mean that they directly took the existing code and took his name out of it? That would be a pretty big no-no from a copyright perspective. (But it also wouldn't do anything, so I assume I'm misunderstanding)
While email as a whole is indeed federated, email service for a single company is usually not, that is you have a single provider and when that provider happens to have technical issues your email might be down. While obviously you could use other provider (or even free email) almost immediately to send emails, you will not be able to receive/access emails that are sent to your primary address/domain until the provider resolves their issues.
Except that email has built in retries and feedback. Also it's expected to be async, so if a server is down for an hour, most people don't even notice.
Yes it has and it is a great thing - hopefully no messages would be lost assuming that downtime is relatively short. This still does pose a (possibly minor) problem when some mails are urgent.
It doesn't really matter how open and federated email is if all mail in/out of your mailbox has to go through one provider. If my company's Exchange server went down, email would stop.
Likewise for Internet service... if my local AT&T connection went down, it doesn't matter how open and resilient the Internet is, I'm not getting online until it's fixed.
I used to work for a relatively small dev-shop (9 persons) and we had two independent internet connections from two providers to avoid such problems. This was because done that way because there was only one fiber provider that wasn't really reliable (3+ hours downtimes every 1-2 months) and mobile tethering wasn't really an option as well because of nearby powerlines that made the reception quite a problem - to the point where our sales guy had to go outside the building during some calls. Luckily there was a second ISP - not really fast (10mbps was the best they could do) and quite expensive (we've paid more than twice more for that 10mbps than for a gigabit fiber), but still cheaper than having 9 people not able to work while waiting for the "main" ISP to solve their problems.
No, Slack is more like sunlight, which also exhibits a single point of failure for most orgs. While the sun does go down, it somehow seems more reliable.
