we are working on it, the thousands of gig workers tuning frontier models

You need to spell and grammar check your writing

lemme guess, you are anti-israel as well

the vast majority of things are on you, if you had a working phone, it would just be install an app, login, and it works

it is better than having to carry keys around

For an office door, why not a key card or lanyard badge or whatever? A code? I feel like you could use something easier than an app too.

You're in a rush in the morning and you leave home without your badge.

Happens to me at least once a month. But I almost never don't have my phone.

Key cards/badges don’t have GPS in them and can’t keep tabs on you outside the office.

it's sold as harder to copy (and easier to revoke when you're doing layoffs - which shouldn't have been a really challenge for card-based systems, they're just old and didn't keep up.)

Neither of these are challenges at all for semi-modern card systems.

Yeah, that article was silly. Yes, setting up a new phone is a giant annoying exercise in yak shaving, but that’s to be expected when transferring to any device.

That said, I’ve had to unlock a door with a dedicated phone app, and it’s always way too many taps even if the app hasn’t randomly logged you out because your session is a month old or because your phone restarted to store an update. (Even more if you prefer to keep Bluetooth off -which among other things saves on battery.)

how does that solution work if the table that is dropped has foreign key constraints?

That's why I said:

> disabling foreign key checks on large operations

And you have to know that, according to your business logic, what you're doing is safe.

Did your symptoms ever improve?

what happens if you suffer catastrophic failure, you'd lose up to one hour of data?

The system had RAID, so disks could be replaced without taking anything down.

We never had a catastrophic failure, but yeah, and hour of lost data wouldn't be the end of the world. For regular maintenance we would just coordinate with the QA team to pause testing temporarily. (Testing was only around-the-clock near a product release.)

how do you know those queries are actually correct without domain knowledge?

Do you know enough about JOINs and how they work to be able to break those big queries down and figure out whether they are doing exactly what you're asking for in English?

You don't, and if businesses start using vibed reports for regulated reporting then I guess we'll see soon what the courts say about that

Litigation aside for a moment - I'm not sure vide-coded reporting could be much worse than what I've seen from early-career analysts in past companies.

You don’t. But you can still check ? ¯\_(ツ)_/¯

i mean that would apply to meeting your SO in real life too, that's just how life works

Well, sometimes. A lot of people just marry someone they went to school with, or worked with, or who was in their friend group or local community. It was simply a matter of deciding to pull the trigger.

Obviously there's still the narrow margin of "living in the same place at the same time", but that margin is much wider than "be in this exact game server at this exact time of day on this exact day".

The margin is wider but the number is smaller. You can be on a hundred different game servers at various times, but you're only born and grow up in an area once.

And some are big “had to happen” (right college choice, wrong WoW faction choice, etc) and others are “the specific had to happen but would have eventually” - if you’re both playing horde on the same campus you’d eventually meet in game or IRL, for example.

My wife apparently swiped me on Bumble by accident

I guess it is AMA, anything except about your current hiring pipeline lol