Ironically, many cars don't have radiator caps, only reservoirs.
Modern cars, for the most part, do not leak coolant unless there's a problem. They operate a high pressure. Most people, for their own safety, should not pop the hood of a car.
What the hell? There are plenty of reasons to pop your hood that literally anyone competent to drive should be able to do perfectly safely. Swapping your own battery. Pulling a fuse. Checking your oil, topping up your oil. Adding windshield wiper fluid. Jump starting a car. Replacing parts that are immediately available.
Not requiring one to pop the hood, but since I've almost finished the list of "things every driver should be able to do to their car": Place and operate a jack, change a tire, replace your windshield wiper blades, add air to tires (to appropriate pressure), and put gas in the damned thing.
These are basic skills that I can absolutely expect a competent, driving adult to be able to do (perhaps with a guide).
I mean, I don't disagree that these are basic skills that most anyone should be able to perform. But most people are not capable to do them safely. Whether that's aptitude or motivation, doesn't matter.
Ask your average person what a 'fuse' even is, they won't be able to tell you, let alone how to locate the right one and check it.
Just think about how help the average person is when it comes to doing basic tasks on a computer, like not install the Ask(TM) Toolbar. That applies to many areas of life.
I have had this new car for 5 months. I haven't learned to turn on the headlights yet. It just turns itself on and adjusts the beams. Every now and then I think about where that switch might be but never get to it. I should probably know.
The prompts for this are pretty sparse. This could 100% be accomplished with better prompting. Even with the current prompts, it's likely I could complete the task with a follow up request specifying what it did correctly and incorrectly. In fact, this could probably be entirely automated with multiple agents checking each other.
It's really only in the last year the LLM's have gotten great and can output massive blocks of code that are functional.
LLM's are at least a 10x speed up on the 'producing code' portion of the job, but that's often only a fraction of the overall job. There's lots of time spent planning and in meetings, doing research, corporate red tape, etc.
For writing code and unit tests, generating deployment yaml and terraform, for me it's easily a 30x speed up. I can do in 1 or 2 hours what would have previously taken a week.
Plenty of people wanted the Cybertruck, it's just that price is too high. It was originally announced to be under $40k, and with incentives, could have been in the $30k's.
It's too broad of a brush to say 'agriculture.' Clearly, some withdrawals have a greater impact than others. Withdrawing from aquifers in arid areas has a greater long-term impact than water from rivers in wet areas.
Wisconsin produces lots of cheese. Are they using water faster than it's being replaced?
Ocean seafood I have to imagine uses near-zero fresh water.
You would think so, but this is actually completely wrong. Prawns and fish use the most freshwater per calorie of any food https://ourworldindata.org/water-use-stress. My point about cows reinforces the point on inequality of impact- the Colorado River is vulnerable and arid, yet we waste this water on cows.
Well, not all fish and shrimp are produced in fresh water, many are produced in salt water (aka, the ocean).
But, It's also likely that most of these farmed fresh water foods are in areas with highly renewable freshwater resources (SE Asia, US South), rather than arid locations.
The map titled "Freshwater withdrawals as a share of internal resources, 2022" shows that SE Asia withdraws a fraction of their renewable freshwater every year.
> Colorado River is vulnerable and arid, yet we waste this water on cows.
Define 'waste.' Producing cows creates food. Rain-grown corn from the mid west is fed to the cows. What should we do with the water from the Colorado River otherwise?
There are plenty of PaaS components that run on k8s if you want to use them. I'm not a fan, because I think giving developers direct access to k8s is the better pattern.
Managed k8s services like EKS have been super reliable the last few years.
YAML is fine, it's just configuration language.
> you shouldn't have to think about scaling and provisioning at this level of granularity, it should always be at the multitenant zonal level, this is one of the cardinal sins Kubernetes made that Borg handled much better
I'm not sure what you mean here. Manage k8s services, and even k8s clusters you deploy yourself, can autoscale across AZ's. This has been a feature for many years now. You just set a topology key on your pod template spec, your pods will spread across the AZ's, easy.
Most tasks you would want to do to deploy an application, there's an out of the box solution for k8s that already exists. There have been millions of labor-hours poured into k8s as a platform, unless you have some extremely niche use case, you are wasting your time building an alternative.
I don't see what the issue is. No one is forced to buy a tesla, no pay for the subscription. It seems likely that self-driving features will require ongoing maintenance and updates for the next several years, it's not like it's 0 cost to them to develop and distribute the software.
I'm not a Tesla fan, I will never own a fully self driving car, but I don't have a problem with a company charging money for features that consumers want. There are about a dozen other car manufacturers in the US alone that can sell self driving cars without a subscription if they want to.
> self-driving features will require ongoing maintenance and updates for the next several years
Autopilot is not self-driving, it is lane-centering with traffic aware cruise control. It has not gotten any maintenance or updates in years, as far as we can tell.
Identical functionality is available from many competitors with no subscription. This is a noteworthy decision for Tesla because AP has long been one of their defining features, dropping it is a big step backward just as the market caught up.
Well, the market will decide if dropping it in favor of a subscription-based upgrade is worth it or not. Not sure why anyone would be upset, this all seems perfectly reasonable.
Many people are exclaiming that the title is baity, but I disagree. It seems like a perfectly fine title in the context of this blog, which is about a specific product. It's unlikely they wrote the blog with a HN submission in mind. They're not a news publication, either.
Modern cars, for the most part, do not leak coolant unless there's a problem. They operate a high pressure. Most people, for their own safety, should not pop the hood of a car.
reply