Readit NewsMy I-PACE cost me over $80k when it was a one-of-a-kind vehicle, an EV from a mature car manufacturer with a luxury interior, sporty performance, hatchback, AWD, and heat pump. It won the 2019 World Car of the Year award (https://www.worldcarawards.com/web/2019_results.asp). It can easily make it the 150 miles from Seattle to Yakima over the PNW Cascade mountain pass in driving snow without needing to stop to charge. It was a bit of a stretch for me to spend that much on a car, but to me it was -- and still is -- a great car.
It wasn't too long before some other EVs with similar characteristics entered the marketplace, and at lower prices. Probably the biggest differences include slightly more splashy range on the spec sheet, although I would argue Jaguar is being more conservative than they really need to be with their advertised specs, and a faster charge rate. In other words, the newer EVs can get from point A to point B with less time spent at the rapid chargers.
Therefore my I-PACE's auction value is almost down to $20k, in spite of being low mileage and in excellent condition. I still get as much range out of it as I did the day I bought it. There are a few reasons for the precipitous price drop, but I suspect the overriding one is that nobody wants an EV that charges at 80kW.
Personally I use my gas car when doing road trips that would otherwise require a rapid charging stop, and I exclusively charge the I-PACE overnight in my garage. So I guess it's still worth a heck of a lot more than $20k to me, which is why I don't think I'll part ways with it until something really expensive breaks on it.
Meanwhile those who have EVs that don't use Tesla's supercharger network are stuck with the likes of Electrify America when they're road tripping. In that case I'm not sure your overall experience is going to be all that better whether your car is capable of pulling 80kW or 150kW at 35% SoC. I imagine people in 6-figure Taycans capable of pulling 270kW sitting in the same line as the $15k used Bolts capable of pulling 50kW for one of only 2 functioning chargers at an Electrify America site in a rural Walmart parking lot to open up, and then the charger ends up only being able to put out 100kW if you're lucky. The charging capabilities of your EV don't mean much if you can't take advantage of them.
Maybe the "unwashed masses" are starting to hear about the horror show that non-Tesla charging networks are as non-enthusiasts are suckered into buying one off the lot without the dealership being completely forthright with them about the true state of things, and that's being reflected in the relative price of used EVs.
Whoever buys it when I sell it later this year will get an amazing car.
The experience was so bad I went to a bottom end second hand 1.0L Citroen with physical tactile controls only. I owned that for 6 years. The entire cost of the vehicle, the ownership, the fuel and all maintenance was less than the depreciation of the Model S in the time I owned it.
A lot of people are hanging on marketing and hope. That's not a safety conscious decision. It's a bad company with bad products and dubious claims.
Musk's antics have turned me off the brand a little but based on my experience, I'd buy another.
- physical servers and VMs
- some microservices
- CI/CD pipelines for every project
- helper scripts
- licenses
- security
- e-mail accounts
- setting up everyone's computers
- wiki and documentation
Moreover:
- understanding compilers and frameworks because "we developers want only to code"
- printer, routers, switches, TV
This is not a rant, just proof for this article.
As a ex-product lead (full stack dev) and head of engineering, the “we developers want only to code” winds me up so much.
Just because your code worked once and now another dev has (badly) applied a framework upgrade, doesn’t mean it’s DevOps’ job to find out “why the build is broken” and fix the incompatibility between your old code and the new framework.
I can’t remember blocking anyone in recent memory and follow ~350 people. I’ve also had some of my best customer service experiences there, typically from places that, without twitter, I’d have to phone and spend hours on hold.
My simple rule for anything on my phone is that I’m extremely tight on what app I give notification rights to. I can count on one hand how many apps have that ability and twitter most definitely isn’t one of them.
If you later decide that the CLI is faster, go ahead. But first, people need to see visually how they can interact with the tree.
I like fork.dev, but most clients are pretty similar at this point.
I used to be a CLI git guy but haven't used it in years now