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.

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.

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.

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."

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.

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

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.

https://vansairforce.net/threads/garmin-emergency-autoland-i...

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.

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."

That's true in two ways: not only are less companies paying to send their attendees to training, but less companies are paying to sponsor these events as well.

Large SQLSaturday events used to regularly get 300-400 attendees, and a good 10-20% of them were new to the field. I would regularly do a show-of-hands in my session asking how many of them were attending a SQL Saturday for the first time, and it wasn't unusual to see half the hands go up.

People learn SQL every day, believe it or not.

I was confused there for a second until I realized you meant "breaks."