Clicking the image expands it. Looks like the real thing to me (and easy enough when you've got the rights; to use AI for this would have been idiotic)
I think the ideal model would be being able to depend on upstream code, but being able to review ALL of the actual code changes when pulling in new dependency versions (with a nice UI) and being able to vendor things and branch off with a single command whenever you need it, so you don't have to maintain it yourself by default but it's trivial when you want to.
It's actually surprising that in regards to front end development the whole shadcn approach hasn't gotten more popular. Or anywhere else for that matter, focusing on making code way more easy to maintain, to compile/deploy, with less complexity along the way.
The train/test split is one of the fundamental building blocks of current generation models, so they’re assuming familiarity with that.
At a high level, training takes in training data and produces model weights, and “test time” takes model weights and a prompt to produce output. Every end user has the same model weights, but different prompts. They’re saying that the constitution goes into the training data, while CLAUDE.md goes into the prompt.
> Use caution when using the manual door release; the window will not automatically lower when the door is opened and damage to the window or vehicle trim may occur.
Manually opening the rear doors is a destructive operation!
Is it actually "destructive" or is it more of a "cramming the door seal over the window and flexing the widow assembly in a way that would result in more failure under warranty than they want if done regularly" type thing.
> To support the cluster’s massive scale, we relied on a proprietary key-value store based on Google’s Spanner distributed database... We didn’t witness any bottlenecks with respect to the new storage system and it showed no signs of it not being able to support higher scales.
Yeah, I guess my question was a bit more nuanced. What I was curious about was if they were fully relying on normal autoscaling that any customer would get or were they manually scaling the spanner instance in anticipation of the load? I guess it's unlikely we're going to get that level of detailed info from this article though.
Neither "roasted" nor "steamed" are completely appropriate for this cooking method.
While there is steam in the vessel, it comes only from the water lost from the meat, not from any additional water, and the meat is heated by the microwaves, not by the steam.
Without keeping a lid on the cooking vessel, the loss of water is too rapid and the cooked meat becomes too dry. Even so, the weight of meat is reduced to about two thirds, due to the loss of water.
In the past, I was roasting meat on a covered grill, where the air enclosed in it was heated by a gas burner through an opening located on one side, on its bottom. With such a covered grill, the air in which the meat was cooked would also contain steam from the water lost by the meat, so the end result was very similar to the microwave cooking that I do now, also preventing the meat from becoming too dry, unlike with roasting on an open grill, while also concentrating the flavor and avoiding its dilution by added water or oil.
> In 2022, the fatality rate for people traveling by air was .003 deaths per 100 million miles traveled. The death rate people in passenger cars and trucks on US highways was 0.57 per 100 million miles.
Planes travel about 10x-20x faster than cars, but that’s still 0.06 vs 0.57. Seems like quite a difference. Which numbers are you using?
https://github.com/zed-industries/zed/blob/main/LICENSE-GPL
reply