
The Next 700 "The Next 700" Papers

Aspiring Abyss Domain Expert

The Next 700 "The Next 700" Papers

Exciting news: we're looking for interns for our formal methods team! Help us turn OCaml into the best language on the planet for writing probably correct code. Hiring in both London and New York. janestreet.com/join-jane-str… janestreet.com/join-jane-str…

The tastiest car dealership I’ve ever visited
Every so often you find an anomaly in NYC, a sacred and untouched space that feels like it shouldn’t belong


Deciding how to help non-expert humans engage with formal verification specifications seems like one of the more important non-verifiable UX problems facing the rise of formal verification. 🧵



I call it “breakfast”
Does this drink have a name: - shot of espresso - in seltzer/soda water - served iced

me: kinda fucked up how many people are offloading their whole lives to muse or instinct or grokbot or whatever claude: yeah

So the log_softmax bug arxiv.org/abs/2610.31642 that's been making the rounds. TorchLean also had the same problem (fixed in github.com/lean-dojo/TorchLe…). How come? This example is pretty illustrative of the proper mindset you need when working on formal verification. 🧵

The MTA has incredible time travel powers. 15 minutes ago, the next R train came in 9 minutes. Now it comes in 5 minutes!

At the PyTorch conference today and tomorrow, come and say hi! We have lots of swag!

potion seller
do NOT go see you can see everything in the first row

Everybody needs to go see You Can See Everything right now

sent myself a text and then got excited when my phone vibrated. 😭😪

After 5 months, 385 citations, and 50 pages I’m excited to finally share the preprint of the survey paper my collaborators and I have been working on: sainati.pl/gpu-survey-prepri… We wanted to put it on arXiv but tragically they don't take survey papers anymore.