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
33 published records
01 / preference
“Kinda obsessed. I, I’ve been using it a lot, even for managing latent space. Like, uh, cowork helps me upload videos and like title things and like edit and everything.”
02 / belief
“I think you guys do something different in planning, but, uh, I’ve been talking with Tariq who is on the cloud co team, and you guys are, he’s like, no, we just exposed planning.”
03 / uncertainty
“We call that MD and agents that MD’s just the same how sim length. And so it is like, that works, but it feels like, yeah, I don’t know.”
04 / belief
“I, I think you still want, especially for people who are doing like high performance software or like very complex software, uh, you still want like, some view of the architecture.”
05 / observation
“The only way to make computer use on your host, like super safe, like really super safe is probably if you approve every single action, right.”
06 / belief
“Uh, you know, look, my, my my, my view is like most things should be Tori by default, unless you really need the full power of electron, but.”
07 / commitment
“I mean, as an engineer I will tell you like, you know, technic a person to technic a person.”
08 / belief
“I mean, yeah, it’s, it’s weird how like, I guess usually I think safety and security is kind of like a boring word to, to engineers.”
09 / belief
“I think you’re, you’re kind of back on the Windows grind ‘cause you’re building out the Windows support.”
10 / belief
“Like sometimes by, by default, some of the theis, I think even early called code, uh, we have to approve every single command.”
11 / belief
“Um, like if the Clark Code people who build the planning functionalities would city, they probably say yes, we have all of those things in Clark code and they do. Um, I think people tend to give cowork.”
12 / belief
“How many, like, it’s always data analysis. And I think the thing that ultimately led to skills is that we wanted to connect this little prototype to our data warehouse and.”
13 / belief
“You know, never say never, but I think going back to this idea of like, we wanna plug this into an entire existing workflow, I think our goal is actually to not replace any of the applications we have in your computer.”
14 / belief
“Mike just joined the labs team as a, as an ic, which I think is very cool and very fun.”
15 / uncertainty
“Um, and I I, we have like Claude Coworks, it might be a GI, I don’t know if we, we have, uh, uploaded it yet, but one of the sessions was like a, like a Claude cowork thing.”
16 / belief
“Uh, but before we get into it, I, I think always wanna start with like a top level.”
17 / belief
“I think for me, this is sort of where I go back to the really basic primitives for our skills are file-based instead of like this complicated thing that exists inside a place somewhere that is like super proprietary.”
18 / belief
“You know, I think, I think you’re right. I think you’re right that the holistic platform is really useful.”
19 / belief
“I’m not sure that I’m like the individual that can add like anything useful there. But I think as societies with economists and, and governments that need to wrestle those questions in a way that is probably more meaningful than me wrestling with them, we’re probably not doing good enough.”
20 / belief
“I think we’re gonna see a lot of like applications and companies that do very impressive things with ai that in the short term might seem very effective ‘cause they’re very specialized to individual use cases.”
21 / belief
“I, I think you can actually do a better job of this. And I, this, this is one shot at my, uh, conference website.”
22 / belief
“I, I think the wild thing is that like as engineers, we so often sort of assume that the platform, like the layer below us is like super stable.”
23 / belief
“I think the funny thing about a lot of these products is that like, for good reason, I don’t enjoy, I, I don’t, throughout my entire career, I’ve never like teased too much what I’m working on because I think you should just like, yeah.”
24 / evaluation
“You mentioned our finance people, they’ve been working pretty hard on very good office integrations. And I think for a while we’ve been like, we built so much tech around cloud, leaving useful comments inside a Google Doc, and now it just does, it just like leaves a comment in your Google Doc and that’s how you interact with it.”
25 / recommendation
“It, it’s, it’s, it’s a level of the stack that I’m quite comfortable with. And whenever I give other engineers, advisors actually that layer that I think is most valuable to invest in because the tools of that layer are not that good.”
26 / evaluation
“The problem is that you need twice the amount of ram, twice the amount of, you know, it’s like, it’s kind of taxing on the machine.”
27 / preference
“Which is like, like obviously I would say that, but it’s also just generally true because I don’t wanna shrink my potential user base artificially by saying, okay, like, I’m gonna start building for the people who are willing to switch browsers.”
28 / preference
“I think there’s been one thing, I use another thing called zo, which is kinda like a cloud computer plus agent.”
29 / prediction
“The price of like writing code is going to zero, blah, blah, blah. But it actually seems like the value of having some sort of platform substrate is like increasing because as you build these new things, you can kind of plug them together.”
30 / commitment
“Um, and I think that’s still evolving, but I think what’s probably gonna go away is like, I’m not sure if it’s gonna fully go away, but I’m gonna say, I think for me personally, I will probably no longer try to come up with a really good product without testing up with people.”
31 / evaluation
“Like, I’m so curious, like one of the most fun parts of my job is like constantly see the weird things people use Cowork for because it’s obviously like very hard for us to actually design for specific use cases we do.”
32 / evaluation
“The reason to go with your own embedded rendering engine is because, and this is still true in 2026, the operating system render engines are not that good.”
33 / recommendation
“If your company’s doing like weird internet things like pack inspection and like, like, you know, taking your part as a cell and inside your company, I think there was probably like a very small, easy version to build of cowork that is much simpler but also breaks on most com most users, computers.”