Noam Lovinsky

But as an example, I used to really love Slack when I was in my startup phase, and there were 10 people in the room, and it was one of the best products that I'd ever seen.

But I have to say, in my role now, I'm not sure that Slack actually

makes me better at what I do and makes my day better and more effective.

And I do worry that some of these things that we're building could kind of go towards that trend rather than actually helping us do things better and taking things off of our plate and kind of removing some of the drudgery of work.

I think that's a very good observation.

And whether it happens widely in knowledge work by 2026, I think is, you know, I'll take a bet with you on that.

Certainly for coding, I think in a lot of places we're already there, right?

I mean, you have like the Ralph Wiggum stuff that popped up over the holiday, and now people are running inference 24-7 for their coding tasks.

for the sort of knowledge work that the majority of us do on a day to day.

Will we be there by the end of 2026?

I might disagree with you on timing, but I think that the insight is correct.

Because I think we're still at the stage where fundamentally we don't have the right UX.

Many people are still at the stage of, I'm not sure what to do with this thing other than search and chat.

I still think that a lot of how people use these things...

it doesn't feel like they actually make them better or that the output is better than kind of what they've done on their own.

I think in most cases, that's not actually a problem with the model or a problem with the technology.

I think it's often a problem with the user experience.

And what I mean by that is, how do you add this sufficient context?

How do you kind of prompt this thing correctly?

Like, what should you use it for?