Sarah Saab: belief

Transcript context

…Oh, interesting. It's amazing to have you both on MLST. MLST is supported by Cyber Fund. I'm a technologist, Enzo's a technologist, you're a technologist, we build software all the time. The idea of having to, traffic in squishy people in order to make our systems go is not immediately appealing, let's put it that way, and I'm very, very sympathetic to that, right? We're all trying to deliver stuff and there's a, you know, accelerating sort of, you know, hot industry around us, and the idea of waiting on a human to tell us if a thing worked feels counterintuitive, and I think our approach to that is stick a really well treated, verified, diversely demographic human behind an API, essentially, and make sure that the structures and infrastructure are there to ensure that human can go fast, understand instructions, and give you something akin to deterministic human in the loop behaviors. But the fact that people are really resistant to this makes a lot of sense to me. I also think somehow in the last 2, 3 years, the stakes have changed, and we now have these very, very inactive systems that are quite non deterministic. And so I think the things we need to do to protect ourselves and each other have also kind of, without us realizing, changed quite a lot. Like, I'm I'm also extremely sympathetic to wanting, like, all these efforts to remove the human in the loop, like, it's costly, it's slow, it doesn't even provide, like, the best quality of data, right? There are several instances where even synthetic data might be surpassing it. But then there's instances where that's also not true, and so what we're actually working towards is a much more adaptive system. There's scenarios where human data is needed, there's scenarios where human data is very much not needed, there's scenarios where you might even have a hybrid solution, or where you meet a certain criteria, you need to have a human in the loop, where you where you almost need to define, I need this level of scrutiny now, therefore, I need higher quality input, and therefore, I it's slower and accepted slower and it has higher cost, and that is fine. So it's almost like we need this routing component there. We we ourselves, we're trying to reduce the lag or reduce the time to data as much as we can and then behind the scenes to ensure that that data can be of highest quality as possible, but at the same time, it's almost like there's a constant trade off between the quality, cost, and time. And if you want lower quality really fast at low cost, you can go with something off the shelf synthetically. If you need something really high quality, it will be the default slower and more expensive. You can get the best experts in the world to give opinions on this, right, or give input on this. But there's also an entire spectrum in between. And so how do we how do we solve for that, make the lag smaller, and make it as adaptive as possible?…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.