The entire UI/UX? We went back in time and basically have a text streamer in a 70's style terminal or existing editor-like situation. If you want to read and (hand)write code, sure, you might be done and be happy with the new variant of what you had decades ago.
replyA UI like Jira/Trello to stage features and see (agentic)team status. A Figma-like UX to actually build out the app/interface/features. A system that aids human review. There's tons of paradigms to explore and improve upon.
there is something "wrong" with the ux that is hard to pin down. these things generate even text summaries more rapidly than i can read them. i need a better method for dumping info into my brain + dynamic control (if necessary)
replyTell it to create html summaries with diagrams and sidebar for navigation.
replyOr ask Codex to create image that explains xyz.
When I take time to read all of the output, I often find that it's mostly noise. I don't like noise so I usually don't bother.
replyBut a person can use subagents, if they want, to filter that down. This burns tokens in a big hurry, but I think subagents can be arbitrary local commands (eg, a local LLM).
Or, you know: Just slow down. :) It doesn't always have to be a race, does it?
Agent farms. Have agents make tons of random high fidelity variations around the clock of the same app or feature from some vague ideas, and you use each of them to see which one you like best and can productize, and you skip the need to do iterative prompts.
replySome of us pay by the token.
replyIs texting your Coding Agent really the final form? Something that watches your interactions or process execution to surface improvements, or whips up prototypes while you brainstorm seems like the next step.
replyNot sure why this was flagged, this makes sense but only if inference gets sufficiently cheap. It would be awesome to see a bunch of interactive prototypes and iterate on the UX before ever building the full app. Historically that's been somewhat difficult even with UX designers.
reply