Zach Lloyd

In terms of collapsing of all the roles, if I had to like design a role for the Uber person who builds with AI, it would be like a product oriented senior engineer.

We see a lot of like product managers and designers who will use the tools to make prototypes.

And that's actually very cool.

But to get stuff to production, I think what you want is like someone who, like I said, more sophisticated than the agent.

And I think there's a real cap on what a product manager or designer is able to build with this stuff right now.

So I guess short answer is I don't really think so.

And if there was like a role I would design, it would be a product minded engineer.

Yeah, so our motion is PLG.

So I think I've overstated how these tools aren't working that well for real devs.

They are working well for real devs.

You just need to learn how to use them right.

What does that mean, learn how to use them right?

Yeah, so if you're someone building in a sort of naive way, and I kind of blame vibe coding for this, what you'll do is you'll be like, build me this thing that looks like X. And the build me this thing that looks like X doesn't tell the agent how the thing should work, at least from the engineering side.

And so if you do this on like a big, complicated code base, it fails or like it produces something that just like wastes a bunch of your time.

It might like iterate and go in circles for hours and finally get you something that like seems to work from a user perspective, but it won't be something that you will actually want to release.

So to make it work in a production setting, it's like you need to tell it how to build it.

And that means you need to understand the code.

And so it's just it's very liable to like kind of lazy usage, which doesn't work well.

Is that a fair concern?

I think it's a totally fair concern if you're doing it the same way on like a code base that matters.