BrentOzar

So, counterpoint: I live in Vegas, and I know firsthand that giving my phone number (which isn’t a Vegas number) at the host stand for check-in has allowed me to bypass lines, every time.

If you frequent restaurants owned by the same company (in this case, José Andrés), you can end up as a VIP, and they’ll treat you differently. I’ve waltzed right up with no reservation, given my phone number, get greeted by name, and get sat down instantly despite everybody in front of me getting quoted a long wait time for the same number of people. Complimentary glasses of champagne, etc.

Even works in other cities.

So I’m just saying, I’m kinda okay with losing my privacy in exchange for that convenience.

Yeah, we use this kind of stuff and so do most of our friends. Makes it really convenient when you go on vacations, want to let friends into the house, want to check on it, want temps to automatically adjust back to normal when your plane touches down in town, etc.

Oh whoa, didn't expect to see this on here. :-D

It works with lots of providers, including local ones.

After you log in, click on your name/picture in the bottom left, Settings, Models. Has a huge list of models supported in the dropdown, plus a "custom model API" tab where you put in the name you want, the base URL, the protocol, and your API key.

Nailed it. I constantly get “cold emails” that were clearly written by an AI that read 2-3 pages on my web site, my LinkedIn bio, and something else on my social media. They all follow the same formula: try to break they ice with something funny about somewhere I took a photo recently, then segue into what I do for work, then offer to help me do it better - usually by offering leads or CRM improvements.

It’s such an obviously repetitive recipe that someone must have published as an example somewhere, and now lots of people (or bots) are trying to follow it, all mining for gold that doesn’t exist.

The cup holder situation, on the other hand… (992.1 owner)

> What if an executive makes a wrong business decision

I jokingly tell students, "We all know executives are gonna make bad decisions no matter what the data says. Might as well give them the random numbers more quickly."

> This is basically the same as saying “databases weren’t designed for interns to run live inline migrations in prod”. Yeah of course they aren’t.

And the same as saying "databases weren't designed for non-technical people to connect with report-building tools like Power BI and Excel and run reports in the middle of peak customer checkouts."

As a DBA, I'm constantly surprised by what people think will be completely harmless to hook up to the database server - and then how much havoc it causes. Gonna be a rough decade.

> Back in the 1970's we'd pull a spark plug and screw in a hose to use the compression phase to inflate tyres.

You'd inflate your tires with a gasoline and air mix?

And why?

Sometimes it's just amazing to look at how much dedication someone put into a list like this, and wonder what they do with this information. It's inspiring (to me at least.)

In a park near my hotel, there's an elderly gentleman who uses a giant brush to paint calligraphy on concrete walkways every morning. He paints it with water - so it gradually evaporates over the course of the next hour or so. I admire his work in the same way I admire this web page.

> I have also seen this used in other formats quite successfully - Fandom/Wikia (used to?) use a MySQL database for each sub-site.

Stack Overflow used it as well, with a database per site (DBA.StackExchange.com, ServerFault, SuperUser, Ask Ubuntu, etc.)

I have a bunch of clients using it. Another drawback with this design is high availability and disaster recovery can become more complex if you have to account for an ever-growing number of databases.

> If you are on AWS and AWS goes down, that's covered in the news as a bunch of billion dollar companies were also down. Customer probably gives you a pass.

Exactly - I've had clients say, "We'll pay for hot standbys in the same region, but not in another region. If an entire AWS region goes down, it'll be in the news, and our customers will understand, because we won't be their only service provider that goes down, and our clients might even be down themselves."

Because I'm sure other people will ask - no, it does not support SQL.

That isn't a new phenomenon.