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!
> 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.
> 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?
> I want everything that passes through a function to be a copy unless I put in a symbol or keyword that it suppose to be passed by reference.
JavaScript doesn’t have references, it is clearer to only use “passed by reference” terminology when writing about code in a language which does have them, like C++ [0].
In JavaScript, if a mutable object is passed to a function, then the function can change the properties on the object, but it is always the same object. When an object is passed by reference, the function can replace the initial object with a completely different one, that isn’t possible in JS.
Better is to distinguish between immutable objects (ints, strings in JS) and mutable ones. A mutable object can be made immutable in JS using Object.freeze [1].
> Our package-lock.json specified the stable version 1.3.2 or newer
Is that possible? I thought the lock files restricted to a specific version with an integrity check hash. Is it possible that it would install a newer version which doesn't match the hash in the lock file? Do they just mean package.json here?
Agreed. The article makes many references to how life would be better with explicit well-defined interfaces… but types are how we explicitly define interfaces.
For example, Rust borrow checking isn’t to add complexity, it is to make it possible to explicitly define lifetime bounds in interfaces.