What other skills do you have and how do you collaboratively work with these skills, um, as a design team?

So we own every...

So there is essentially, we have skills that are global for the whole company.

So the engineering team maintains a bunch of skills, uh, we want engineers to use for specific things like QA, security.

There is a bunch of skills that are, allows engineers to do their work on a day-to-day basis.

Um, we wanted to do the same for design.

And my team, we started this whole project called Search Intelligence.

Yeah.

Uh, it w- it was kind of around the line for what is codifiable versus will always require human judgment, and is 85% the line you have in your head of what is feasible to get that to? Or is it a matter of time? Like in, in a few months, will you be able to get it to 90 or 95%? And I guess I'm trying to r- really understand the, the sort of human leverage, uh, in the process of getting something live, especially something that is built by an engineer that has AI judgment connected into it in some way.

I still think it's... [sighs] I think it's a matter of time.

I still think it's gonna be 85% for a long time because humans are really good at like- Creating patterns between multiple things they see.

You know, like just spotting, you know, spotting the things that are related to each other, and having critical thinking to say, "Actually, I don't think this is the right thing to do for this user, because I've had a conversation with that user, and, uh, uh, and this is what they're actually referring to." So there is, there is...

The decision-making should be, like, it's human.

It's a critical thinking to spot whether you're tackling the s- the right problem.

Like, one of the things I tell people sometimes in this is like, "You should read." Everybody should just read.

Do you have a sense of what that future looks like for the shape of this role and this type of infrastructure layer?