3 ms·

> When passing an entire design specification into an LLM and receiving a new representation token by token, generating a response would take several minutes,

> When passing an entire design specification into an LLM and receiving a new representation token by token, generating a response would take several minutes, making it impractical. Woe is me, it takes minutes to go from user-designed mockup to real, high-quality code? Unacceptable, I tell you! But seriously, if there are speed improvements that you can make and are on the multiple-orders-of-magnitude then I do get it, those improvements are game-changing. But also, I think we're racing too quickly with expectations here; where minutes is unacceptable now when it used to take a human days? I mean, minutes is still pretty good! IMO.

willsmith72 3y ago
From experience developing with GPT4, minutes would be too long for me. I use it for exactly this use-case, converting mockups to code, but you need short feedback loops. It will get things wrong. There'll be things it misunderstood, or small tweaks you realise you need after it's done its first job. Or maybe it misunderstood part of your design, or just needs extra prompting (ALL CAPS for emphasis, for example). Even after multiple iterations it will extremely rarely be perfect, which is fine, because once it has a decent readable solution, you can obviously take ownership of it for yourself. Where minutes might be fine would be in a "handoff" workflow, where designers do design and then handoff to devs. 10 minutes in between of AI processing to get something for the dev to start on would be acceptable, and the dev could then take that first attempt and using GPT4 refine it a bit. But I don't really like handoff teams anyway..