Hacker News new | ask | show | jobs
by chvid 4 days ago
As I understand Jane Street they have done great things for OCaml and they also do their own web framework (I guess that big money bin needs a lot of dashboards).

I think the designer here takes a wrong approach and sort of falls into engineer envy where he wants to make prototypes as deep and realistic as possible. And that is not really the most important part of the design job.

The most important thing is that the right thing gets build (why do we need a JSQL input box? what do we actually want? what are other ways to do this?). And this is often better done with pen and paper sketches, meetings, observation, discussions ... rather than too quickly narrowing on a particular design and spinning into discussions on whether buttons should be on the left or on the right, LLM intricacies etc.

2 comments

Taking it slow with paper and interviews works if you think about what you're doing. The other option now is shut down brain and press the slot machine lever one more time. One of the designs has got to be good soon.
This. LLMs helping implement many ideas is a curse and the results speak for themselves.

As a non-designer I want to see a thought through 1-2 ideas, not 10 ideas you coded with llm and now the burden of thinking which one is better and why is for some reason is on me.

(I’m the author) making ideas legible and testing them with users is part of the design process regardless of tooling. You can summarize this article as “I find LLMs more effective at making ideas legible vs figma - for the work I’m doing at Jane Street”. This has helped me iterate and it helps me test with users and get better feedback from them. I’m not just prompting “make no design mistakes” over and over.
No matter how nuanced your your workflow is, there are some people on HN that just hate AI and will see it as "slot machine go brr" no matter what you say. It is generally pointless to engage with such people.

Great article, by the way.

And there's people that just complain that others don't see enough nuance to everything, applying zero nuance themselves.
People are much better at saying what they don’t want rather than thinking about what they do. It’s more effective to throw everything in using LLMs, then using human judgment to sculpt away.
>> It’s more effective to throw everything in using LLMs, then using human judgment to sculpt away.

Not really. Maybe its effective from designer side but from other side that has to review all those ideas it is exhausting and counterproductive. Especially when it is in code.

You really don't need a real prototype for most things. Simple visual is more than enough to present an idea and explain etc. In fact, it is often much better as you can see all flows in canvas at once.

With interactive prototype to see all flows of a feature you have to go through each one, which again is very uneffective.