Some credit cards like American Express offer their own insurance as part of the membership fee as long as you pay for the rental with their card, and decline the coverage offered by the rental car company.
3,765 karma · joined May 21, 2011
Some credit cards like American Express offer their own insurance as part of the membership fee as long as you pay for the rental with their card, and decline the coverage offered by the rental car company.
Yes, and even better, don't design the ring by yourself. Get a nice jewelry box for the diamond, use it for the proposal, and when you open the box, say:
"Our relationship is something we're going to build together. I want your opinion on everything for the rest of my life, because you're going to be my partner. I got the diamond, but let's design the ring together, you and I, because this is too important for me to do by myself. I need your help."
They'll melt, and the ring will mean even more.
Unlikely, just as Solarwinds wasn't finished when they distributed malware that got government agencies hacked. You underestimate the slow turning radius of giant company purchasing departments.
The books really are that bad. I think less of someone when I know they've written a book for Pakt.
Yeah but that's from Shein, and you don't wanna buy your nukes from a company that uses child labor and unsustainable materials.
Everyone's going to feign ignorance. The container owner will say they didn't realize the container had been stolen from their property, or they rented it to someone who's responsible for whatever they do with it.
The property owner will say they didn't give anyone permission to put a container there, or that they rented it to someone else.
The destination can be just a port, and a moving company can be hired to pick up the container from the port.
(Source: my spouse shipped a lot of stuff from China, and I was horrified at how little security and documentation was involved. I can see how cars cross borders so easily.)
Because sometimes it's not about the query you pass in - it's about a new data type, for example. The layer may think it understands the query, but may not be able to handle the format of the results, or may cache them incorrectly.
For example, when SQL Server added the JSON data type, one of my customers found that the caching layer mangled it for some clients, but not others, or would return the correct result the first time, but the cached result was formatted incorrectly.
Another problem can be the connection itself, like when SQL Server added support for Always Encrypted, an end-to-end encryption method.
Be aware that there are hundreds of open issues[0] and dozens of pull requests [1], some of which involve clients being unable to connect or not supporting all components of the SQL language. Just because your database supports something, doesn't mean your caching layer will.
It gets really ugly when a new version of your database comes out, with brand new features and language enhancements, and the caching layer doesn't support it. It may take months, or in some cases years, before the caching layer is feature-complete with the underlying database. If you want to use some of those language enhancements, then your app may have to maintain two connection strings - one for the caching layer, and one for direct database queries that the caching layer doesn't support.
Your support teams need to learn how to diagnose problems with the caching layer. For example, this issue [2] talks about the level of work involved with understanding why newly inserted data isn't showing up in selects.
I hope they succeed and deliver the concept, because it's one of the holy grails of databases.
[0]: https://github.com/readysettech/readyset/issues [1]: https://github.com/readysettech/readyset/pulls [2]: https://github.com/readysettech/readyset/issues/39
Nothing in the Github feature roadmap for either one, either.
Part of the reason is that Toyota uses really conservative, classic engineering. They sell things that have worked well for decades, and they're hesitant to introduce new features.
That's also why their infotainment systems are notoriously terrible and they lagged years behind everyone else on selling electric cars. Gotta take the good with the bad.
In car fan circles, this is called a “sleeper” - a car whose boring design and boring color doesn’t draw attention from police. That’s not a negative at all - it’s great! Car fans often buy sleepers on purpose.
Historical sleeper examples include the Ford Taurus SHO, Chevy SS sedan, and Audi S6. I had a 2003 Audi RS6, a notorious sleeper. Looked totally plain, but could absolutely fly, and I never got a ticket in it despite some truly hair raising speeds.
It can’t go a whole lot worse than how the current trial is going, and that’s his gamble.
They didn’t. They waited until the EU made them switch to USB-C.
Reminds me of the time [1] Fusion-IO showed how good their drives were for SQL Server by running benchmarks with just 16GB of RAM enabled, even though the servers had 384GB RAM.
Under direct questioning, they admitted that if you just used the rest of the RAM in the server, their drives didn't have any effect, and that's why they limited the server so badly for the presentation. (sigh)
Try to find a 2010 Prius with over 300,000 miles. There are only a handful in the US because they fall apart long before 500,000 miles.
Depreciation isn't just about the car's value - it's also about the amount of mechanical work you have to put in for the suspension, tires, brakes, etc during the time that it goes from 150,000 miles to 500,000 miles.
My mom's 2010-era Prius is a good example. The dash displays failed at around 100,000 miles, and she bought a new car rather than pay $2,500 to have the dash pulled out and display replaced.
Got jobs elsewhere, started consulting, etc.
Yes, and for decades, it's been a bad idea for SQL Servers that grow over time.
When you store files in the database, you massively inflate the size of the data file and the transaction log. It makes all your maintenance tasks take longer: backups, restores, high availability, disaster recovery, corruption checking.
To make matters worse, when a new version of the file arrives, people never overwrite the existing file - they store the new version as a new row or object, and keep the old version around too. Space requirements explode exponentially.
If you're dealing with a 10-100GB database, sure, it seems fine at first. But after you start storing files in there, you won't have a 10-100GB database - you'll have a terabyte-sized one, and that's when your maintenance task heartaches begin.
No, the business will be closed. It would just serve as an archive of history.
$38K is an insurance policy that will keep the marketing front end of your company's site online "forever", long after you run out of VC money and shutter the company. Keeps your vanity up and running, your fond memories.
It turns your hosting costs from a monthly expense to a "permanent" capital expense that's already paid for.
Today, maybe. For the human costs of hosting support in 2123, given the cost of inflation, it might not be, and these plans include technical support.
(Although you could also that the technical support work on most of these 100-year plans should be dropping over time too - especially if the human being involved passes away. You could even argue that AI might be doing the technical support in 2123.)
Meh, groups taking short rides in long SUVs like he talks about here, that's a good time to catch up on social media before everyone's face to face again.
Sustaining group conversations in a long multi-row SUV is painful. Get your social media stuff done briefly, then when you get out of the car, go back to interacting in person. This is fine.
My ex-wife was a US air traffic controller, and the training they go through is stunning. They're tested continuously for years, with something like an 80% wash-out rate.
During testing, they get 1-2 tests per week, working a shift just like a controller would, with fake pilots on the radio, and real computer systems. If they let airplanes get even remotely close to each other, they fail. If it happens twice, they're out of the FAA, immediately, permanently. One of the instructors told me, "It's my job to make sure your wife has the worst week of her career, every week, during training - so that when she's actually on the job, every week will seem easy no matter what she's facing."
Even just in training, you could see the stress take its toll on the candidates over the years.
I assume you mean OBD (on board diagnostics), not Ol Dirty B*stard, who has a very different set of codes.