Rohan Jha
574 posts

Rohan Jha
@Robro612
Research Intern @mixedbreadai | PhD Student @jhuclsp Interested in IR & NLP



Hierarchical pooling is very strong to reduce the footprint of late interaction without degrading results We recently showed that training for MUVERA/SMVE improved performance retention What if we trained for hierarchical pooling? We get even stronger (5×) lossless compression!

The MAIEUTIC Lab (maieutic-nlp.github.io/website/) is @aclmeeting and looking for new members. If you are interested in joining, please fill out this form: forms.gle/82bkj5Nf9QQEXx… If you are in person at ACL 2026, please fill this one out as well: forms.gle/1vRn3N14qXPXh6…




I think Claude's (Sonnet, Opus, Fable) weirdest behavior is, when iterating on a document it will constantly include references to prior versions of the document that no one will ever see. Like: “This replaces [X] and better handles the objection…”








can't imagine how much this very first side event of icml seoul went viral lmao



I find the Lakebase design for serverless Postgres very elegant, so I spent some time explaining how it works in this blog. The blog starts by explaining how databases really persist data (with a write-ahead-log and data files that are updated async), and how Lakebase separates storage and compute by externalizing those two components. It ends with how the Lakebase architecture naturally leads to LTAP, enabling OLTP and analytical workloads against a single governed copy of data. My goal was to make it readable by anyone curious about how these systems work, not just database and storage experts. That turned out to be a lot more challenging than I first thought. Database storage is one of the most complex areas in computer science (the ARIES paper cited in blog was the hardest paper I personally ever had to read). The first draft had too little detail and I couldn't land the ideas. The second had too much and I'd lost anyone who isn't already a storage expert. This is the third draft, and I'd love feedback on whether the depth feels right. databricks.com/blog/lakebase-…






