@waleswoosh it's largely the trend of seeing our parents and the generation older than us get into dead end jobs, watch everything get more expensive, get 2-5% raises every year in their 9-5s then get laid off almost pretty surely. and realizing their parents wasted away without enjoying
@dutweets@duCares
Agent with name "Ola" blocked my other twitter account after requesting her to call me. 45 minutes since my first DM she has sent a message every 10 minutes and didn't even reply to my question
Is this how you do your support? You block the customer online?!
Nailing the UX for AI Agents is one of the more fun design questions and challenges that we’ve ever had in software.
As AI moves from just being about Assistants you talk with, to full Agents that execute complete tasks for you, the nuances of the AI Agent design are going to matter more and more.
This shift requires some fundamental rethinking of software design as we enter a world where a near unlimited amount of workers can be interacted with that are operating autonomously. Here are a few of the major options that seem to be popping up:
1. The AI Agent just becomes another user in the background in the workflow. In this scenario, the AI Agent can be dropped into a workflow as a participant, essentially as a superuser. In these scenarios you tend to interact with the Agent much like you would a person in that same workflow, and the UI affordances remain mostly unchanged from the end-user perspective — work just seems to be “getting done” by another user in the system.
2. The UI fades into the background and you mostly interact with Agents in a chat interface like we’ve seen in areas like Deep Research. This one is potentially the most ambitious, and it works fine when you can farm out an entire Agent task and expect a complete result at the end. But a lot of the onus is on the user to know how to best prompt the Agent, and there are limitations on users being able to have a complete sense of where they are in the workflow.
3. The software morphs to be part Agent conversation and part UI. We’ve seen this paradigm seemingly take off with products like Cursor, Windsurf, Replit, Claude’s Artifact, and others where the UI seamlessly mixes the workspace for the user and the communication for the AI Agent. This UX seems to work well when in single player mode, collaborating with an agent, but we have limited examples of how this works in more complex environments.
4. The user interface begins to feel more like a tool to manage AI Agent work as opposed to the AI Agent sitting next to the user doing their work. This one makes sense in scenarios where you can deploy AI against problems in parallel and the effective management of the AI Agent workflows becomes the primary task in the system.
At Box, we’re working on a mix of the above (where most relevant), and I suspect most software will be a hybrid of multiple of these approaches for a while. At this point in software we have more questions than answers, but it’s extremely fun to watch the different patterns play out.
Why do people care if code is written by a human or not? We were generating code procedurally for decades (the code is written by other code) and nobody gave a shit. Compilers are programs writing programs. What matters if it actually solves the problem or just pretends to do so.
@mrioszbo i dont get who is buying this shit? has anyone ever confirmed his revenue claims?
it's not cope i admire the hell out of him. just seems crazy to not admit that he's only able to do this bc hes famous, and b, who the hell is paying for this slop just bc hes famous?
@DigitalPsyche@DanFriedman81@BoringBiz_ yet no one says crap about these frat boy types or question their job roles or their knowledge and nobody questions their qualifications when theyre posting pics working from a hotel room, from home or from the beach
@DigitalPsyche@DanFriedman81@BoringBiz_ i love how the post you quoted is literally the exact opposite of what youre trying to say
so in contrast to 100,000 wfh beach surfer guys posting their digital nomad lifestyle, these girls were *supposed* to create content *as part of their job*
@MattWalshBlog babies dont get invited not because someone hates all babies (people literally about to get married and start a family). babies dont get invite because some of their parents are really bad or inadequate
@zack_overflow information without opinion is not useful
someone who doesnt know something doesnt know the right questions to ask or what to prompt for
the model responds based on the guidance received, and has no opinion either
stackoverflow has swe's screaming why they hate a language