Terminal UX: How Warp is modernizing command-line workflows

Transcript

I think most software engineers that want to use some type of. AI capabilities today are using 3 interfaces that are all fundamentally text based. They're using their editor. They're using their terminal and they're also using some type of chat experience. Now maybe sometimes there's a more couple than others, but but but there's kind of often 3 and they're all text based the. When I look at warp I think. Gosh, this, there's this like weird blending. My vision is we're moving to a world where it's like developers job is gonna be telling the computer what to do. And I think putting aside whether or not it's through a terminal or an IDE or through chat GPTC desktop app or whatever, I feel like the interface that needs to exist is one that is geared towards. Um, me coming in as a developer and being like fix this bug and then in parallel being like. Um, look at this feature that's described in this ticket and help me start on that. And then maybe in parallel, help me understand this error that I'm seeing in production and you sort of have like a bunch of these tasks that you're managing. And when those tasks kind of need your help, you step in and help them. But for the most part, they're sort of running and your, your job as a developer has gone from like typing all these commands manually or writing all this code manually to sort of like supervising what these. I'll call my agents, for lack of a better term, are doing and helping them do the job. That's like what I think the next evolution is like. I think that's in the next, honestly, next year. Year and a half, two years, I think beyond that, I don't really know. I think it kind of could get, it could get crazy.