Hacker News

points by x3haloed 1 day ago | 0 comments

Here's the thing. As you're indicating, UI and UX are not the same thing, but they're both subjective.

You can ask the model to implement common patterns for both UI and UX. You can ask the model to correct obvious UI errors.

But you can't really ask the model to have UI taste unless you supply that taste, and you can't ask a model to "do UX" in a vacuum. UX work requires user testing. So any UX workflow that is going to be handled by agents must also include observational data of humans using the software.

There is no set of instructions that can do "UI/UX" without also incorporating human feedback.

[–] andyfilms1 1 day ago

The problem I've been having is they just have no sense of systems, which is exhausting once your app scales to anything beyond 1 page. It will happily write features that can't interact together at all, despite being in the same piece of software, and burn tokens to glue them together when you point out the problem.

And obviously you can say, "hey these features need to work together make no mistakes." But for really big projects like professional software, that's a LOT of features with a LOT of possible interactions.