Ian Lim
1K posts

Ian Lim
@IanCLim
AI health | prev AI + neuro @stanford

We’re officially in our new Era.

📣 Update: we raised our $60m Series B from @Lux_Capital, @IndexVentures and @01Advisors, with participation from @sequoia, @eladgil and @BainCapVC . When we came out of stealth 283 days ago, we had negotiated contracts worth $30m for our clients. As of last month, that number is over $1 billion. We work with the most ambitious companies in the world, including @tryramp, @clay and @RogoAI. Today, we want you to hear from some of them directly. Contracts are the rails of commerce. @crosbylegal is a hybrid AI law firm that gets them signed 80% faster. We’re announcing our Series B to keep scaling the dream law firm.




Don’t ask Sequioa about Applied Compute’s revenue





feeling really bad for the Meta OS team


If you're thinking about AI-generated UIs, recommend checking out JELLY by @YiningCao3, @peilingjiang, and @HaijunXia. My favorite kind of work: both a compelling system/demo AND a bigger idea that people can build on! talk video: youtube.com/watch?v=X3cf1U… paper: dl.acm.org/doi/10.1145/37… tldr: vibe-coded UIs aren't ideal for users generating software, because it's hard to steer the generation and keep things consistent. They propose solving this by first generating a more structured model of the user's needs, including a data schema that the user can see/edit. Then UIs get generated based on this schema, but it feels more like fluidly composing premade widgets in a task-specific way than building a new "application". Reminds me of @alexobenauer's work on an itemized OS and @jasonyuan's Mercury concept, as well as the Embark system that I worked on. The demos feel compelling and magical, but there's also enough technical meat to see how this is actually feasible today with LLMs. Really cool. Things I'm not so sure about: - I like formality on demand: super unstructured representations (text, drawings) and only adding structure when needed. It seems like Jelly jumps straight to rigid relational models. Good fit for some tasks but not all. I wonder about fitting in less-structured bits and then structuring on-the-fly with LLMs. (As a mitigating factor: the fact that you can edit the schema live on the fly does help a lot, blurring the line between using and creating the software. And structure is really useful for things like different views of the same info) - I'm curious how much the exposed schema ends up really being useful to users for understanding. Their own user study found the majority of users just relied on the UI rather than the schema. Feels like there's a lot more work to do here to achieve deeper interpretability. The challenge of "how do you tell users what software does without showing code" is endlessly deep...









