Finding some balance between access and safety for vibe-conjuring parts of the OS in a way that's still powerful but won't accidentally nuke or corrupt itself.
603 karma · joined August 21, 2017
Finding some balance between access and safety for vibe-conjuring parts of the OS in a way that's still powerful but won't accidentally nuke or corrupt itself.
>What sits behind them is a calibre I had to solve the way a real one is solved, and this is why I bother.
>A skeleton is a load-bearing machine with the metal taken away down to the last safe gram, so what is left is whatever carries a force, and no spoke is wider than its job.
>Running and buildable are different questions, and the second is harder.
>A drawn movement is a claim. Before anything gets a surface, I test it as a machine.
If this isn't Claude-prose then the author has been reading too much of it...
(oh, Pangram gives the entire thing 100%)
I have to imagine if there was some internal Polymarket-esque platform I’d be a rich man... (facetiously speaking) Unfortunately knowing the way the wind blows is not as much of an asset to those in charge.
This is almost certainly due to the photographic/human likenesses of actors being under an entirely separate license and royalty contract than pure IP from Disney.
Gen2 autonomy stack is completely unrelated to Gen1, and from what I hear is a completely different level of reliability.
(also - this presentation covered yet another, unrelated, gen3 autonomy stack, which shares none of the hardware or models with the existing gen2 stack, either.)
- Ten em-dashes
- "not just A, but B"
- wasn’t just a vacuum cleaner; it was a small computer on wheels
- they didn’t merely create a backdoor; they utilized it
- they hadn’t merely incorporated a remote control feature. They had used it to permanently disable my device
- incessant bullet points/markdown-style formatting- And an overly dramatic/promotional tone
Obviously the image is AI as well, but /shrug
Six flowery “from-to”s in one article:
>from beginners to seasoned professionals
>from seasoned backend engineers to first-time data analysts
>from GPU acceleration and distributed training to model export
>from data preprocessing with pandas and NumPy to model serving via FastAPI
>from individual learners to enterprise teams
>from frontend interfaces to backend logic
And more annoyingly, at least four “not just X, but Y”.
>it doesn’t just serve as a first step; it continues adding value
>that clarity isn’t just beginner-friendly; it also lowers maintenance costs
>the community isn’t just helpful, it’s fast-moving and inclusive
>this network doesn’t just solve problems; it also shapes the language’s evolution
And I won’t mention the em-dashes out of respect to the human em-dash-users…
This stuff is so tiring to read.
(This is mostly facetious)