I'm excited to announce I'm joining @OpenAI! I left Robinhood in March of 2025 to embark on a wonderful year and a half long career break. I used that time to: travel (I went drifting in japan!); build a low-latency arbitrage bot on Solana, briefly becoming the 60th most profitable arbitrage bot on the chain; and learning @leanprover in service of building an accurate model of rust to prove `unsafe` rust code was free of UB! But a lot has changed. For one, most engineers I knew were, at the time, leveraging Github Copilot as an "intelligent autocomplete" to accelerate parts of writing code. Software was (and at many places, still is) manually reviewed, and there was much doubt, especially from myself, that models could ever improve to the point to economically handle the more complex tasks of implementing entire features, proving conjectures, or discovering, and exploiting, novel 0-day vulnerabilities. Clearly I was wrong! I've been shocked and inspired by the rapid advancement going on in the industry while I was away. One thing has been abundantly clear: security is changing. I'm excited that I get an opportunity to work on some of the most important problems facing our industry today. And I get to play a meaningful part in discovering, and contributing, to the next generation of strategies required to secure this burgeoning technology.

lol

we've built an entire industry on sand castles and it's about to rain

crossover event for my two interests

making either incredibly stupid or incredibly dumb moves rn 👀 will update this post if it goes through

eMudhra playing 4d chess

Excuse me?

The beautiful thing about the PHP bug is that all it takes is one dedicated hero to use the CVE to defeat the CVE (mitigate public facing PHP systems on their owner's behalf)

This isn’t a “I’ll do it tomorrow” thing. It’s a “we are 6+ hours late to calling a SEV0” thing. Mitigate this **now**.