3 ms·
I'm becoming increasingly convinced that you need a purpose-built LLM to generate usable UI code. There are ways to use LLMs to increase efficiency and velocity
by pc86 1y ago
I'm becoming increasingly convinced that you need a purpose-built LLM to generate usable UI code. There are ways to use LLMs to increase efficiency and velocity without sacrificing quality, but they're all at the API/backend/service/whatever-you-want-to-call-it level, or in the initial planning stages.
I basically use LLMs to plan work, then to do the backend work with close supervision, then I do all the UX stuff completely on my own.
- chrisweekly 1y agoThat's really interesting. I feel like that runs counter to a broader perception that vibe-coding the FE / UX is straightforward, vs more challenging backend stuff. As someone whose 27-year career began with - and remained largely centered around -- client-side / FE / UX, it's of particular interest.
- pc86 1y agoI've "vibe-coded" a few small hobby projects, and use cursor sometimes for professional stuff, and it always collapses for me on "real" front-end tasks. Yeah I can say "give me a layout of a certain style" and it will do reasonably well if it has no existing constraints. But for example, I vibe-coded a UI and then tried to adjust the tailwind theme it picked, and it was an absolute nightmare. You would have thought "change the primary color from A to B, select a new accent color that is darker than what you've selected and is not A or B, and now update the dark theme to be comparable" spread across multiple prompts was one of those crazy 3d animation puzzles you see used as a way to break LLMs.