I think Jane Street is an Anthropic investor, so take it fwiw.

Even for the large products, figma is not the starting point for new concepts anymore. I start with a quick prototype on dev environment and then share it with designer for further improvements in figma or in the app itself. With every new model or agent improvement, going back to figma for polishing the ui is decllinig. If we can find a way to keep the frontend code static templates without complex logic, need for this polishing in figma will go away completey as llms can understand it one context window. With the modern frameworks designed for client side rendering, keeping everything in one context is still tricky.

The benefit here is designers learning to code. It was always weird to me that designers were shaping software without knowing how it was built. I'm a designer btw.

However, designing in code is technology-first. One could argue that the purpose of design - to shape the artifacts for human purpose - is better done NOT starting with the strict rules of code. Pen and paper is still hard to beat, not for anything that looks nice, but for helping your mind forward.

Even if this is ad only - are we really ready for a rug pull from Anthropic? Maybe I’m completely unaware in this tools space, but I feel like it’s last tool that’s worth (and not pricey)…

> Claude gave me free, unlimited iteration, unbothered when I changed my mind for the 50th time or asked for a small tweak

Do you not pay for Claude?

I worry about Figma stock, I know some who bought during the IPO who are now underwater. Figma launched their own design agent but not sure how well that's doing.

I use the same approach a lot. Before AI I also did this manually. First sit down with a user and just paper and pencil, then hack together a frontend POC / demo, have them play with it and adjust until it works as they wanted.

For me building a quick (not production quality) frontend demo in code was already often faster than getting the right interaction working in Figma. And it allowed to make it fully interactive so you can catch much more edge cases on the UX side.

Now with Claude Code it's even faster to build the throw away prototype. But not a huge difference since discussing with the users and thinking about how it should work is 80% of the time. Claude maybe halves the other 20% compared to quickly doing it yourself. Faster to first version, slower to iterate if it didn't fully get it.

We are doing this on my team (I am the frontend engineer) and honestly I really miss the old way of doing things.

Written specifications are being reduced in favor of these working prototypes, and now there’s this extra cognitive burden of reading the code and trying to determine what were the intended changes, and what’s the slop that needs to be tossed aside.

We also have to figure out, should we take over this generated PR and make any needed changes? Or do we start over from scratch? There’s often a sense of friction either way.

There have been times where a bunch of unintended changes were generated and I took time to port them over on my reimplementation, and then later on it’s “oops! Sorry! We didn’t mean to change that.”

I get it’s empowering but it does take away from some of the joy I used to find in my work and replaced it with some headaches.

Sounds like desk strat RAD work is moving to LLM gen code at JS. My recentish experience of that kind of work has been Athena at JPMC and Quartz at BoA; both Python with functional style via DAG or pixie with py ui framework to match. Which enables quick dev of the parts of trading workflow that don't need to be quick, like booking tools or EOD risk. I know first hand Athena and Qz are crufty when you get into the weeds. The bonsai framework with Elm inspired ocaml impl sounds v cool. So I can see how this approach can accelerate a lot of trading tech dev. But does it have any traction over the hard problems where we turn to C++ or Rust: near real pricing and risk across multiple instruments and markets?

I don't see how a coding model competes with figma TBH, an image model maybe but that's a stretch too.

i gave claude code my design system that i built in figma and haven't opened it again. it's much faster designing with your voice.

Figma make and gpt designer have a bunch of catching up to do. I couldn’t even import our brand guidelines into make which is already a .fig like what are we even doing here, guys? CD crunches through ungodly amount of tokens and is really slow on iteration but at least you can get some really nice prototypes extremely quickly there. GPT beats any Anthropic models on illustrations so they really should get a grip on multimodal. Overall, it seems like we’re still super early but you can already see glimpses of what may come

I’ve been using Claude Design for my front ends. The output looks and feels good enough, but the designs often look very similar and generally adhere to contemporary web tropes.

Keen to hear if anyone has had unconventional creative adventures with it.

Same here. I mostly use Figma for logos and random assets now.

I'm my work as an FDE this week, Copilot did the initial UI. Feedback was given and tells were adjusted all through prompting.

amyone know how to use claude design more effectively I always alhave a feeling I use a slot machine

from 6 sessions and 5 projects only one template that I choose anything else is really really bad

> Oh no, Figma ER was actually positive, release mode SaaS FUD

Is it just me or the bar to publish janestreet blogposts has been lowered recently?

I use codex

Honestly, I'm not really pro or anti llm and I think there are a ton of limitations for using it to generate code, but UI has been probably the only thing I've been able to vibe code. It helps that I've done a lot of UI work over the years, but I think the combination of defects being easily visible through normal usage, the UI being a non-critical component of a system (bugs don't cause vulns or data corruption (usually), combined with the amount of churn that UI's see, make it a somewhat uniquely good candidate for vibe coding. Also a lot of UI toolkits are declarative, and I think language models do much better with declarative code.

In a way it's not much different from copy-pasting components from templates or whatever, just with more customisability. And for stuff that isn't HTML-based like React it does worse. It's also not great at building component libraries, I still write those myself with little LLM involvement, but that makes sense because the architecture is actually relevant with that, unlike generating CSS and xml-derived components, which is mostly just declarative templating anyways.

I've had decent success writing the core logic myself and then delegating the UI to AI. I think if I didn't write the core logic it would not work very well, but since it's designed well by myself the AI has a much smaller scope to work in which constrains it enough where vibe coding works. Pretty cool.