1,672 karma · joined November 24, 2016
The above routine is a specific practice to remember something — I basically think it would be effective for anyone that actually did it, and almost all non-adherence would be at step zero.
If you are a skilled mathematician, it is quite easy to verify both that (as of 7th April) models excel at novel calculations on held out problems and mostly shit the bed when asked for proofs.
Gary cites these USAMO as evidence of contamination influencing benchmark results, but that view is not consistent with strong performance of the models on clearly held out tasks (arc test, AIME 25, HMMT 25, etc etc).
If you really care, you can test this by inventing problems! It is a very very verifiable claim about the world.
In any case, this is not the pundit you want. There are many ways to make a bear case that are much saner than this.
the bull case very obviously speaks for itself!
I downloaded their data from the metr public evals GitHub repo and independently re-implemented the very basic maximum likelihood analysis, which gave very similar results to what they shared.
In particular, we examine the one-step iterative process of DDIM [39, 19, 21] and show that it has limited capacity with respect to the target timestep under the current denoising network design. This can be addressed by adding the target timestep to the inputs of the denoising network [15].
Interestingly, this one fix, plus a proper moment matching objective [5] leads to a stable, single-stage algorithm that surpasses diffusion models in sample quality while being over an order of magnitude more efficient at inference [50]. Notably, these ideas do not rely on denoising score matching [46] or the score-based stochastic differential equations [41] on which the foundations of diffusion models are built.
That said, even in their cherries the emphasis still isn’t quite right in the Tolkien example.
I feel like the current version is fairly hazardous to students and might leave them worse off.
If I offer help to nontechnical friends, I focus on:
- look at rate of change, not current point
- reliability substantially lags possibility, by maybe two years.
- adversarial settings remain largely unsolved if you get enough shots, trends there are unclear
- ignore the parrot people, they have an appalling track record prediction-wise
- autocorrect argument is typically (massively) overstated because RL exists
- doomers are probably wrong but those who belittle their claims typically understand less than the doomers do
A) The type system is fairly bad, as type systems go (forgivable) B) the type checkers are, for large codebases, excruciatingly slow, to the point that the tests are faster!!
The second is not forgivable.