Latent Space / episode intelligence
Speakers in the public record
Claim mix
Evidence policy
Every row below preserves an exact excerpt. Identified speakers are linked; unresolved voices are labeled and excluded from people counts.
Claim ledger
34 published records
01 / evaluation
“That works well, of course, but that’s not really the most, um. I would say that’s not the product that, that drives revenue.”
02 / belief
“I think we’re sort of just moving up the abstraction ladder and then the human role becomes more about observing and maintaining the outer system.”
03 / belief
“I mean, it needs to be something that is, you know, human readable and I viewable and I think that’s pretty key.”
04 / belief
“There’s something there. I think that’s, that’s really important. So it’s, we’re trying to sort of.”
05 / belief
“I mean, that was, I would say that was a big learning is just, you know, really be, be savvy and really careful thinking about what the model wants in terms of, you know, its environment and, and, and cater around that.”
06 / belief
“I think that’s, that’s pretty fundamental, but I would say like a lot of the, the bad things about it can be fixed.”
07 / belief
“I think one thing that’s becoming more clear is I think like, like, uh, coding agents are the kernel of EGI, sort of, everything is a coding agent.”
08 / belief
“I think. I think we’ve been pretty successful with that. It, it’s just a matter of like, like staying nimble.”
09 / belief
“I mean, we try to make it as easy as possible to set up, but we want it to be pretty deep and sophisticated. And I think a huge part of that is the operator needs to be able to interrogate.”
10 / belief
“I would say if there’s been like a general arc where, you know, it’s like you gradually strip away everything.”
11 / uncertainty
“I don’t know why. Um, but the other thing is that, like, I I was just talking about this with a peer, like how much is ranking important versus like, uh, being able to do parallel exhaustive queries.”
12 / belief
“I think the quality difference that’s interesting is, um, even though companies that say they’re selling the same, a, it’s really into like quanti quantization, but like companies that say they’re selling the same model through different vendors, whether it be through first party or Bedrock, Azure, et cetera.”
13 / belief
“I would say turning point, I can think about like the week and a half that we all came together on this as we were building custom agents, was that alignment that we’re not trying to build for everyone here.”
14 / belief
“The other thing I would say is the, um, you know, unlike a lab, we aren’t fully incentivized just for you to use as many tokens as possible.”
15 / belief
“The, the CEO’s gonna force everyone to wear a wristband look, I mean, the slice of the problem that, that we care about is like, you know, can the company have all the context of what everyone said at every single meeting, and then use that to, yeah.”
16 / belief
“Um, what’s difficult is like that market that I think right now is no man’s land of where reasoning models were six months ago, that the nano haikus, et cetera, haven’t caught up to, because now we’re just paying more for those, um, for like extra capability that we didn’t necessarily need and so are our customers.”
17 / commitment
“There’s a, I won’t say which coding Frontier Lab, but there was a point where he had like outlived like the thread length and context length uhhuh that that coding agent provided.”
18 / belief
“I think if it would be a mistake to like, like fix it on any, any particular coding agent.”
19 / belief
“I think there’s, there’s definitely a lot of use cases where, where you don’t want like a full coding agent with a compute run time.”
20 / belief
“I think that’s, that’s pretty interesting because if you, if you had a model that really knows your company, I think that would be like a huge quality uplift.”
21 / belief
“I, I, I think that like we, we really closely partner with the Frontier Labs on capabilities and we also have to have strong conviction on, as those capabilities move.”
22 / belief
“I think every software engineer in notion this summer went through like this, um, sheer, um, one of our engineering leads of the company called it, like every software engineer is going through the, the, uh, identity crisis that every manager goes through, where all of a sudden they realize their ability to write code is less important than their ability to delegate in context switch.”
23 / belief
“I mean, but auto is heavily, I think what’s actually been hard for us is to tell convince people that auto is not just our cheapest, dumbest model, but actually the model that’s best for the task that you wanna do.”
24 / uncertainty
“Uh, you, you, you just have a lot of comments. Uh, you, you, uh, I don’t know where you wanna start.”
25 / evaluation
“I think there’s like two different versions. So one is like, we just have a, a, a solid bench of senior engineers that come and go on what we call the Simon Vortex and Productionizing what we built, right?”
26 / evaluation
“With notion, it’s almost like more of the expertise is at the edge because you as a platform, you’re like so horizontal that the end user is not really the same.”
27 / preference
“We literally change our tools every single day and if we notice an issue, we will, we’ll, we’ll, we’ll fix the problem.”
28 / evaluation
“Like there’s a lot of platform work that we do need to, like solidify a little bit. So sometimes it’ll be in dev for a couple weeks before it makes it to prod just because we still have to like, make it robust, make it HIPAA compliant, ZDR compliant, figure out the right contracting with the vendor, whatever it is.”
29 / preference
“Alessio: Yeah, the open-endedness I think is like, the main thing is like, well, if I go write code to just call an API, I would never use an MCP.”
30 / preference
“Um, slack and linear and Jira search and notion that is not using necessarily the search MCP functionality that is provided by those companies. And that’s because it’s quite critical we think, to how our agent trajectories work is for us to have a little bit more control on the functionality of the search journey.”
31 / preference
“Um, but it’s because we’re thinking about the fact that our users to do their, to do their daily work, need to export PDFs, not because we’re like, Hmm, I think a computer tool could be cool.”
32 / preference
“I, I think we, you know, like, like generally, generally the way we do these things is, you know, you first make it possible, maybe like a sort of janky way. So I, I, I think the way I set ‘em up is like, you know, we created like a new database that was sort of like issues mm-hmm.”
33 / preference
“Like, we want you to decide if you want to have Opus Auto Triage all of your emails, we will actually give you nudges in the product to rethink if that’s the right choice.”
34 / evaluation
“We, we sort of designed our own like, like tool calling framework and then we tried to fine tune the models to, uh, to use it over multiple turns. Um, and because it, it didn’t work well out the box, I think.”