2,434 karma · joined May 11, 2018
All due respect to Jan here, though. He's being (perhaps dangerously) honest, genuinely believes in AI safety, and is an actual research expert, unlike me.
2. Tribalism + scale + time = two "us vs them" groups. Politically, FPTP voting mathematically implies spoilage; the Ron Paul example doesn't extol some virtue.
3. People are furious due to these (utterly preventable) things: https://www.youtube.com/watch?v=qEJ4hkpQW8E
Horsepower comparisons here are nuanced and fatally tricky!
Crucial context:
- They're only looking at image models -- not LLMs, etc
- Their models are tiny
- A "concept" here just means "a noun." The authors index images via these nouns.
- They didn't control for difficulty in visual representation/recognition of these exceptional infrequent, long-tail "concepts."
If I didn't know an object's label, I too would struggle to identify/draw it...
1. Generate inverted problems which are easier to produce than solve. For instance, create an integration math exercise by differentiating a hairy function and reversing the steps.
2. Create (simulated) environmental data.
3. Use adversarial model competition, e.g. self-playing chess or training an artificial image generator/detector model pair.
There's evidently a commonplace myth that information quality starts pristine and exclusively gets degraded by systems thereafter. That's just easily, demonstrably false in myriad ways. That's why it's absurd to conclude that LLM output being in internet training data will cause model collapse.
Information-rich synthetic data can be created without humans, and it works. (Check out Phi, for instance.)
There's nothing substantive in this article. The author expresses a seething hatred for OpenAI's CEO by repeatedly lampooning ("where's the evidence!?") brief quotes, without context, of Altman's opinions/predictions. I hope that the author escapes whatever rut made him so overwhelmingly bitter and resentful. I've been there, and it truly stinks. :/
1. Engineering the generalized solution, then
2. Carrying the cognitive burden of this new indirection layer, and finally
3. Ripping out this premature -- and so likely wrong -- abstraction
Premature abstractions are like alcohol: fun borrowed from the future, and paid back later with interest. If unavoidable, choose the abstraction most narrowly scoped to your actual code base, not a future one. Humans suck at prediction. Ask me how I know.
Plenty of STEM jargon existed which Shannon chose to not use.
The unhealthy thing here isn't the marketplace, it's government policy. If you eschew popular open-source tools for closed/proprietary alternatives, this will happen. Linux will always have several orders of magnitude more experts banging on it than Windows ever will. Vendors pontificating about security will not change this fundamental asymmetry. Also, don't want product lock-in? Don't choose vendors with a significant risk or history of lock-in. Don't endorse face-eating leopards and then blame others when they eat your face.