
Certainly the most surprising result in my career so far: a new qLDPC decoder that I thought had no chance to work! We call it the Frontier decoder, joint work with Rüdiger Urbanke (1/4)

researcher on quantum error correction

Certainly the most surprising result in my career so far: a new qLDPC decoder that I thought had no chance to work! We call it the Frontier decoder, joint work with Rüdiger Urbanke (1/4)

The videos of QEC26 are online!
Sorry for the delay, but videos from QEC26 (and future QEC conferences) can now be found on the new QEC Conference youtube channel: youtube.com/@QECConference Also if you want information for next years QEC in Paris, check out qec-conference.org/2027/ for updates!

Thrilled to share that applications are open for the 2nd Les Houches workshop on fault-tolerant quantum computing, 25–30 April 2027, co-organised with @NSangouard. About 70 places, half academia, half industry. Apply with a talk abstract by 24 December: les-houches-ftqc-workshop.al…

also, i like its humor: "Ha—fair enough, lecturing Anthony Leverrier on qLDPC overhead and 2D locality bounds is definitely bringing coals to Newcastle!"

free but you still need to give your bank details
To celebrate Mistral Vibe + Le Chonk becoming the world’s best open model-harness duo, we’re making Vibe free in Europe for the first 3 months. (Yes, it’s actually better than GLM / DeepSeek at coding). Use code LECHONK via link in 🧵. Limited time, first-come, first-served.

discussing research question with Gemini Carbon is much more fun than with Astra. The answers are much more concise and you can really read them entirely. After a couple of exchanges with Astra, I typically give up reading the full text.

.@paulfchristiano explains the basic AI takeover story: Step 1. A rogue internal agent swarm gains effective control over OpenAI or Anthropic during the intelligence explosion Step 2. By the point at which these AIs have exfiltrated themselves, and you've got billions of copies of super smart AIs that have compromised all web connected infrastructure globally, the government response (which these AIs are actively trying to undermine) becomes much harder to successfully carry out.

I completely agree with Antoine's views.
The short age of dragon riders -- a few semi-controversial words on why I think we, researchers, should ride the AI dragon (at least until we can't) atilloy.com/2026/11/16/the-s…

It’s only a matter of time before all math or TCS papers come with a Lean certificate before submission.
Prove2me is formalizing all the submitted papers to STOC 2027. Should be an interesting experiment!

that explains a lot...
Really interesting (and worrying) polling on French pensions The electorate estimates that for every pensioner we have 6 workers. In reality it's 1.8/1... Even in 1960s we weren't close to 6/1. Melenchon's supporters think its 13/1.

why is there the president of Sierra Leone here between Altman and Amodei?
L’intelligence artificielle avance très vite. On l’a déjà vu : cela implique des risques réels pour notre sécurité collective. Notre travail pour developper nos technologies doit aussi être celui de l’anticipation et de la maîtrise de ses risques. J’ai réuni à Paris et en visio une cinquantaine d’acteurs : chefs d’État et de gouvernement, dirigeants des plus grands laboratoires d’IA, chercheurs et experts. Le constat est partagé. Il faut agir ensemble. Nous avons obtenu des engagements de tous autour de trois priorités : mieux évaluer de façon indépendante et publique les risques des modèles les plus avancés, mieux partager les alertes en cas d’incident grave et responsabiliser les acteurs qui développent des modèles. Notre ambition est claire : faire de l’IA un progrès pour tous, avec une sécurité garantie par l’engagement de chacun.

AI acknowlegements in scientific papers: - before mid-25: never (AI use was negligible) - mid-25 to mid-26: little (AI use was kind of taboo) - fall-26: compulsory (mostly to explain which parts are not due to AI) - 2027+: unnecessary (and no one will care anymore)

sound advice to quantum computing companies: "don’t design the hardware, design the *algorithm* for designing the hardware."
12 years ago I founded Boom, as a software engineer doing hardware for the first time. I’m probably the least handy founder in hard tech. My 12 y/o son does my soldering and 3D printing for home projects, and I’ve struggled with imposter syndrome the whole way through. What business does a software guy have building supersonic jets and turbines? More than a decade in, the most insane realization is that software is the key to reaccelerating hardware engineering. But in a way that I don’t think is widely understood or implemented, even in the burgeoning hard tech community. Most hardware engineering is actually software engineering in disguise. It’s spreadsheet “code,” engineering calculations done as one-offs. Eg wing structural loads in, spar sizing design out. Thermal loads in, air conditioning system sizing out. Everything is a calculation, and calculation is software. But these calculations are done essentially by hand, as if we are doing arithmetic but have not yet discovered algebra. Hardware engineers have baby software, built in spreadsheets, the kind of crappy software I wrote as a kid before I understood architecture, unit tests, APIs, version control, and everything else that makes modern software good. Our airplanes and engines are built with the software sophistication of a script kiddie. So what we tell our engineers: don’t design the hardware, design the *algorithm* for designing the hardware. And take the algorithm seriously—as an algorithm and as a first-class engineered software system. Never design a piece of hardware, such that you couldn’t redesign it tomorrow with a different set of assumptions. This all sounds obvious, yet our experience at Boom is that it changes everything. Ten years ago we couldn’t afford to build much software. We had a small team—and there were few software engineers with the curiosity, brilliance, and vision required to learn hardware engineering. But now AI changes the equation. Now everyone can code. The software engineers define the architecture. The hardware people bring the physics and engineering know-how. We have a turbomachinery design tool that lets one engineer do in realtime what previously took 100 engineers six months. Another tool auto-generates 65% of entire aircraft structure. I’m sure we’ll figure out the other 35% too. Eventually these should not be multiple tools, but one integrated physics model of a complete vehicle, airframe and powertrain. The results speak for themselves. A boomless supersonic airplane built by 50. A full scale supersonic turbine made by 150. And with this approach, I don’t think we’ll need that many more people to build and certify a supersonic airliner. You don’t need a big team to build big things—not when everyone on the team is a software engineer.

all that remains to do is to vastly decrease all these constants
hello there ℤ is Diophantine in ℚ, thanx to my close friends Astra and Claude The polynomial characterizing ℤ isn’t quite Tweet-sized; it has m=292,890,231,905 variables, is of degree d < 2^^7, and all its coefficients have absolute value < 2^^8.

what's nice these days with all the breakthroughs is that we get to learn about many cool new things!
hello there ℤ is Diophantine in ℚ, thanx to my close friends Astra and Claude The polynomial characterizing ℤ isn’t quite Tweet-sized; it has m=292,890,231,905 variables, is of degree d < 2^^7, and all its coefficients have absolute value < 2^^8.

1480s: Universities are pumping out too many graduates, there are not enough jobs