Every argument clarity score on this site is built from rows on this page. Each
question and answer was assessed with names hidden, the host's own answers included, on
four things from 1 to 5:
directness (does it answer the question asked), coherence (do the ideas follow),
precision (concrete details and clear references), compression (says a lot per word). The weighted
mix (30/30/25/15) is the exchange score. A person's published score averages their exchange
scores on raw tape only, at least 8 of them, shrunk toward the cohort mean.
Full method →
Answered raw tape
D 5 · C 5 · P 5 · Cm 4 4.85
Q What do you think just gets, just becomes part of coding tooling?
A I think there's going to be a class of tools where you sort of start from the front end. This would be things like Lovable or Bolt or Replit or maybe even Figma Make if you're coming from the design side, and you'll have like an all-in-one platform for Build an app or even like, honestly, like build a business, like put payments in it. It's like, it's kind of like the evolution of like either a Shopify storefront or like WordPress or Squarespace or something like that. So I think that's all going to be bundled more on like the core pro developer side. I can't tell if it's going to be a world of like MCPs and integrations and like all these tools sort of interplay. That's one approach, or it's going to be more like there's enough alpha and like You put all of these things together. And I think warp is a little bit more like this. Like we're trying to build a single pane of glass, for instance, for doing like local agents and remote agents.
AI assessment note: “I think there's going to be a class of tools where you sort of start”
Answered raw tape
D 5 · C 5 · P 4 · Cm 4 4.60
Q And how do you think about the different parts of the coding market? There's vibe coding, there's professional code. Like they're all, there's all just one thing. Are these separable things?
A I think it's, Pretty separable. So for Warp, our target is pro developers building, like, software that's economically meaningful. So we, we really want to, like, focus on actually people who are using agents to build kind of hard apps, uh, apps that might, like, Go into your Mac doc or be pinned as a Chrome tab as opposed to vibe coded apps where I think it's more of a long tail play. And so I do think by the way, it's, it's awesome that anyone can code at this point, but I think if you look at where most of the value is in the software market, it's, it's not in those long tail apps. It's in like a relatively small number of apps that are super heavily used. And that's my background. Like I, you know, I've worked on one of those apps, Google sheets and just like, I have a lot of passion in terms of helping people build real apps. It's much harder, by the way. Like, I think it's relatively straightforward at this point for a good agent to like, you know, with relatively few prompts, build like a web app. It's much harder to apply these agents successfully to pro code bases. Um, so that's where we're focused.
AI assessment note: “I think it's, Pretty separable. So for Warp, our target is pro developers”
Answered raw tape
D 5 · C 5 · P 4 · Cm 4 4.60
Q And as you think forward and forward in terms of all these different tools and all these different use cases and vibe coding versus professional coding and that the role of a software developer, Where do you think we are in two, three years?
A Yeah. So the, the way that I'm thinking of it is there's sort of three phases here. For most of my career, we were in like the world of develop by hand is how I talk about it. So my workflow then was like, I would open up a code editor. I would find files I want to change. I would type some code. Uh, I'd have some assistive features and then I would go back to the terminal and I would type commands to build that code. And I think we're switching away from that to something like develop by prompt where I start most of the coding tasks that I do right now by prompting an agent, and that agent does some work. And I think there's a third phase, which is like, automated development. Honestly, I think that's like, Kind of the bigger market here and why people are so excited about this space is you can actually use these agents to automate some parts of the software development process. And so that's like, you know, cognition does that. We're moving into this space cursor as background agents. Um, the rate at which this stuff will happen is like not super clear to me, actually. Like the, the most recent iterations of the models, in my opinion, were not as big of a step change. As like, for instance, when like Sonnet four came out, that was a really big step change in coding capability. I think there's going to be a mix of interactive and automated pieces of development for a while. I,…
AI assessment note: “within a couple of years, you'll have everyone working by prompt”
Answered raw tape
D 5 · C 5 · P 4 · Cm 4 4.60
Q And why do you say that? Is it because you need to correct errors that the agents are making? Is it because things may be architected in a way that isn't scalable?
A Is it something totally, so it's like, it's like the agents, you can think of them kind of as junior engineers. So If you didn't have someone who was senior watching them, you end up in a situation where these agents will make code that creates bugs. It could create security issues. It can cause your code base to become really unmaintainable. And so there's actually like a premium right now on these senior engineer skills where you can architect, where you can review code, you can make sure the system doesn't degrade. And so again, I would be, if I were like early in my CS career, I would be racing towards building that expert Where you don't want to be, I think is like someone who is just like perpetually in the junior engineer state. Cause I do think that's at risk.
AI assessment note: “these agents will make code that creates bugs. It could create security issues.”
