> but literally every site with passwords can do that by default, it just needs a general admin UI which almost always exists.
Most sites/systems that are designed for security won't have such an admin UI - passwords should generally not be handled in a way where anybody other than the user is ever able to know what they are.
"I can erase a securely hashed password and set a new one" is very common and generally seen as safe, and does not at all require being able to "know what [the current password is]".
You can store passkeys in a password manager where they're either in a full-time shared config or there's some configuration that allows access if something happens. (e.g. Emergency Kit for 1Password, legacy contact for Apple account, etc.)
RAV4 and other Toyotas have insanely good residuals that make up for any upfront price difference, and you don’t look like a cop all the time when you drive around town.
The Explorer is incredibly dated at 5 years since the last refresh with the RAV4 getting a refresh/redesign this year. Every reviewer I’ve seen knocks the Explorer for lack of interior refinement.
No need for a CVT when you can get a Mazda CX-90 with a real transmission. But I’d also take a Grand Highlander over an Explorer any day.
Predicted reliability of Ford vehicles is a joke compared to Toyota. You’d actually get a more reliable car with a BMW, it’s embarrassing. If you don’t believe me pay attention and count how many 1st generation Ford Fusions are on the road versus second generation Toyota Priuses. The Prius is bulletproof. The Fords are in junkyards.
edit: Oh, crap, I mixed up the Explorer/Escape because the Escape is the Rav4/CRV competitor. I think the Escape is underrated. Not particularly familiar with the Explorer.
eCVT and CVT aren't mechanically similar. Personally, I'd only consider cars with manual/eCVT/EV transmissions.
> RAV4 and other Toyotas have insanely good residuals that make up for any upfront price difference
Yeah, that's a consideration if you frequently flip your cars, I kinda forget about that because me and most of the people I know keep their cars long-term. e.g. I just got rid of a 2011 Fiesta - there isn't enough residual value maintenance savings in a 2011 Yaris for me to have ever come out ahead with one of those.
Unfortunately by correcting your misremembering, I’m even less convinced. The Escape is even further down the ladder in its crowded and competitive class of vehicle.
The Escape isn’t underrated it’s just rated properly.
There’s like 6 or so cars that rank above it for various reasons: CRV, RAV4, Sportage, CX-5/CX-50, Forester.
Even Mitsubishi put out a better vehicle than Ford with the Outlander if we go by Car and Driver’s scores.
I’m sure you can get one with some sick discounts but Ford also has company there with Nissan, Mitsubishi, Chevrolet, and I’ve even heard Mazda runs strong discounts depending on the dealer.
I was going to make a similar point - the math changes quite a bit if you're a multi-car household - in that case it absolutely makes sense to have at least one vehicle that's a short-range EV.
My household is a newer hybrid Ford Maverick and an older ICE Impreza (that gets worse fuel economy than the Maverick) - if we were replacing the Impreza today we'd probably go for a 2026 Leaf or a used Chevy Bolt.
I had a 2004 WRC that we replaced with the IONIQ 6. The Hyundai is a great upgrade, and let us keep AWD. We could get by with less range on that car, but for now we just take the truck if we are going more than 100 miles one way.
> Sure, maintenance is a thing, but honestly, flinging java, docker and a few other things onto a build agent isn't the time-consuming part of maintaining CI infrastructure.
Depending on your workplace, there's a whole extra layer of bureaucracy and compliance involved if you self-host things. I aggressively avoid managing any VMs for that reason alone.
Luckily, at work we are this layer of bureaucracy and compliance. I'm very much pushing the agenda and idea that managing a stateful, mutable linux VM is a complex skill on it's own and incurs toil that's both recurring and hard to automate. The best case to handle that is to place your use case into our config management and let us manage it.
Most modern development workflows should just pickup a host with some container engine and do their work in stateless containers with some external state mapped in, like package caches. It's much easier for both sides in a majority of cases.
Even if batteries were very cheap, you run into scaling issues where your battery pack ends up very heavy, so then you're using increasingly more energy to lug your heavier battery back around for everything that isn't long-range towing.
> Even if your job isn't hauling, per se, if you work on job sites you wanna be able to haul stuff. Imagine if you showed up to your new Tech Lead job with an 8 year old Chromebook. You'd look a little bit silly.
Hey now, my 8 year-old Pixelbook still has 2 more years before it's out of support.
Not more secure, but some sites mandate email/SMS 2FA, don't support TOTP, and have added passkey support.
For these sites, using passkeys is materially more convenient than copying 2FA codes from email/SMS.
reply