Joel Hron

I do.

I think we sometimes just human nature index on like the minimum versus the viable word in that acronym or in that pseudonym.

So I think, you know, not to say you don't want to ship fast and like you don't want to try to like build simply and that kind of stuff.

I think those are all good core, like agile principles that teams should continue to follow.

But

I do think, you know, at the early days, trying to take the blinders off and really, like, scope a big, hard problem and see what, like, build all the components, see what the agent is capable of.

And then when you see, okay, this is where it feels like it's fallen over, like, that's when you maybe dive deeper and spend more time focusing on an individual component.

But, like, try to put all the pieces together first and then dive in.

Yeah, it's a good question.

And I agree for what it's worth.

I think deep research is one of the most profound examples of agents in an application today.

I think there's a reason for that, though.

And that is because that is the highest agency use case you could possibly imagine.

Like, you know, a user's entering this situation with no preconception or maybe some small preconception as to like what the right answer is.

And you're just scanning the universe to figure it out.

And so the agent has full agency to go out and use its tools and use its content and use maybe its system knowledge to figure that out.

And so you're not constraining the agent in any way.

So I think that's why it's such a profound use case.

You know, you asked a question about like hallucination risk and how do you build confidence in lawyers and things like that early.

I actually think that the agency dial is one of those ways as well.