> All that said, I don't see an inherent reason to stick with a single sensor modality beyond the complexity of integrating multiple streams of different types of information While cameras can exceed the human eye, typically the human eye is more mobile, so you'd need a system that allows the cameras to move in 3d to be able to really get to human experience. (Since humans can decide "the glare is washing everything out, let me move my head" to take advantage of a different angle or different access to shade)

> Once and for all people: "it's" (with an apostrophe) is a contraction of "it is." It's (it has) been awhile since I've been able to "well akshually" a post on what "it's" is.

I've been testing various tools over the last couple months and I've had this sort of thing happen several times, but it was mostly just annoying because I could roll back easily enough. There were two cases where one app (Cursor in case case) after weeks of use randomly decided to stop asking me to approve updates to code, and decided to just directly apply a code fix itself. And then it further went on to execute the amazon cli and proceed to wipe out part of my dev environment with it's broken update. (I was pretty sure I'd had it set to always confirm before executing code, but that didn't seem to protect me) It apologized similarly. Did it matter? Not really, being a dev environment. It still hurt though for the wasted time, and because it changed the environment I was troubleshooting a very hard to reproduce bug in, and it took a long time to get back to a condition where the bug was debuggable again.

There are some products out there that are only certified to run on VMWare if you're virtualizing.

>The problem is that Microsoft uses servers not listed in its SPF record (include:spf.protection.outlook.com ) to send to itself. If they're DKIM signed, DMARC doesn't require SPF to pass though.

I wasn't suggesting that's the most fulfilling way to work for everyone. But the previous post was listing that as a work ethic issue... ie, something to get fired over. Why should someone get fired for doing their job? If "identifying issues" was part of the job, that should be listed, at least implicitly, as part of the job.

> do the absolute minimum to not get fired I don't understand the problem. That sounds like they're meeting the requirements of the job then. If you want more out of people, that would be a different set of requirements, no?

Maybe they could have a mother-drone that flies above them tethering power down? (which can also scare away birds that try to eat the robobees)

Last I checked, Bitwarden didn't allow administrative control of domain equivalence though unfortunately. So if you're using it in an org/enterprise, you'll have to ask your thousands of users to each set that up. (And god forbid the list of equivalent domains ever changes) I'd really love to find a password manager that has administrative control (or at least influence) of equivalence lists, that plays well with subdomains. (so you can make internalsite.company.com equivalent to company.okta.com and newbranding.okta.com, but no other *.okta.com would match) The closest I found in testing was LastPass... but their subdomain magic and strict equivalency rules didn't play well together.

If you're using a password manager, just generate a random string for each security question and store it in your manager.

There are plenty of non-Apple watch faces available, some costing significant money.

For a company like Verizon? You refer the person to the appropriate department and you're done. They have folks who handle this sort of thing day in and day out. I wonder if this was a rep at a non corporate store (franchisee or whatever they're called), and they didn't do all the training required of them. (because I'd be shocked if Verizon didn't have _something_ in their requirements to cover this sort of thing)

One reason could be taxes. Different countries (and different states/etc within countries) each have their own taxing requirements on people and companies. If you wander from a country where your company has a legal presence to one without and then to a different one where they have a presence, taxes can get really messy. And countries really care about their taxes.

Job conditions changed, so they left their job, presumably for one that fit their conditions better. (or in search of one of the many ones out there) The article doesn't say they're suffering because they quit. So why was it a foolish decision?

They push Google Drive Backup, which will automatically backup certain folders from your machine to your drive. If you're a Mac user and drop applications in there, you can get a great many files given how app bundles work. If you're a web dev, your node project could have a great number of files as well. Now add in that some businesses will transfer files from an employee to their manager when they lave the company... and you've got VPs who are collecting files like crazy. It would surprise me for 5m files to be common, but having a few people run into the limit legitimately doesn't surprise me at all.