Speakers in the public record
Claim mix
belief 15evaluation 6uncertainty 5observation 3commitment 3prediction 2preference 1
Evidence policy
Every row below preserves an exact excerpt. Identified speakers are linked; unresolved voices are labeled and excluded from people counts.
Claim ledger
The useful parts, with receipts.
35 published records
“This has been my experience with platform teams in the past, where you have an envelope of acceptable build times and you let it go up to breach and then you spend two, three weeks to bring it back down to the lower end of the average low bed stop.”
- Publisher
- Latent Space
“I’m also calling back to there’s this like levels of EGI I don’t know if Opening Eye is still talking about this, but they used to talk about five levels of EGI and one of it was like, oh, it’s like an intern coding software patient.”
- Publisher
- Latent Space
“In the same way, you would have a full stack engineer be able to drive a feature from the backend all the way to the front end.”
- Publisher
- Latent Space
“I’m not gonna open up a id, I’m not gonna do anything. But I will say, okay, fix this little thing, change a line, change a color.”
- Speaker
- Not verified from transcript
- Publisher
- Latent Space
“I think like the only argument I have against this is basically scale testing, which obviously the larger pieces of software like Linux, MySQL, he calls up even the Datadog and Temporals and then maybe security testing where Yes.”
- Publisher
- Latent Space
“You make a pipe errors versus the standard, standard out. I don’t know. Okay. Whatever.”
- Publisher
- Latent Space
“The structure of the repository is like 500 NPM packages. It’s like architecture to the excess for what you would consider, I think normal for a seven person team.”
- Publisher
- Latent Space
“There’s a lot of customization, but there’ll be multiple unicorns just doing this as a service. I don’t know.”
- Publisher
- Latent Space
“We were up in the five to 10 PRS per day per engineer. And I don’t know about y’all, but like it’s very taxing to constantly be switching like that.”
- Publisher
- Latent Space
“I would say like a. A couple thousand line dependency is a thing that we could in-house No problem.”
- Publisher
- Latent Space
“I think we’re excited to do We’re gonna talk about Symphony in a little bit, but like the way we distribute it as a spec, which I think folks are calling Ghost Libraries on Twitter.”
- Publisher
- Latent Space
“I think your intuition is right, that it’s very great for spiking out prototypes, exploring ideas quickly, doing those documentation updates.”
- Publisher
- Latent Space
“All the coding review agent, it can merge autonomously. I think that’s something that a lot of people aren’t comfortable with.”
- Publisher
- Latent Space
“I was briefly part of the, that, that world is it salt? I don’t know. It’s actually really hard for humans to agree on what revenue is.”
- Publisher
- Latent Space
“I had to go do a crash course in Beam and Elixir, and I think most people are not operating at that scale of concurrency where you need that.”
- Publisher
- Latent Space
“We expect that there will be some harness things there. Agents, SDK is a core [00:59:00] part of this to enable both startup builders as well as enterprise builders to have a works by default harness that is able to use all the best features of our models from the Shell tool down to the Codex Harness with file attachments and containers and all these other things that we know go into building highly reliable, complex agents.”
- Publisher
- Latent Space
“I had a mental reaction when you said don’t put the agent in a box. So I think you should put it in a box.”
- Publisher
- Latent Space
“I think obviously you can spend the whole day going through some of these, but I do think that some of these have a lot of care or some of this you might wanna tell people, Hey, take this, but, make it your own.”
- Publisher
- Latent Space
“I will say that the coordination layer here was a really tricky piece to get right.”
- Publisher
- Latent Space
“Exactly. That’s these are my road roadmaps for a e wherever people hiring engineers, I will go.”
- Publisher
- Latent Space
“The level of complexity of the dependencies that we can internalize is, I would say low, medium right now.”
- Publisher
- Latent Space
“Coming back to the final point I wanted to make is, yeah I think that there, there are multiple other, like you guys are working on this, but this is a pattern that every other company out there should adopt.”
- Publisher
- Latent Space
“I was gonna go back to your, I think the demo videos that you guys had was pretty illustrative.”
- Publisher
- Latent Space
“I think one of the concerns I have with that kind of stuff is you think you’re making the right call by making, it’s persisted for all time across everything.”
- Publisher
- Latent Space
“Let’s introduce Symphony. I think we’ve been mentioning it every now and then. Elixir.”
- Publisher
- Latent Space
“Super excitedly part of the Bellevue Community building the future in Washington. And I would say that there is lots of work to be done in order to successfully serve enterprise customers here in Frontier.”
- Publisher
- Latent Space
“It’s almost like you’re, it’s like a ratchet. It’s like you’re forcing build time discipline, because if you don’t, it’ll just grow and grow.”
- Publisher
- Latent Space
“For us as users, it has again, pushed the productivity five x, which means I think there’s something here that’s like a durable pattern around removing the human from the loop and figuring out ways to trust the output.”
- Publisher
- Latent Space
“Which means that often over the agent trajectory, I realize the bits that we’re missing, which is why I find I need to have this synchronous interaction.”
- Publisher
- Latent Space
“The tech jet tracker and the quality score are pretty interesting because this is basically a tiny little scaffold, like a markdown table, which is a hook for Codex to review all the business logic that we have defined in the app, assess how it matches all these documented guardrails and propose follow up work for itself.”
- Publisher
- Latent Space
“Yeah, and I think success for the way we are [01:08:00] operating here means the model gets better taste because we can point the way there and none of the things we have built actively degrade Asian performance.”
- Publisher
- Latent Space
“If you think that code is context, code is prompts, it’s better from the agent behavior perspective to be able to look in a package in directory X, Y, Z, and it not to have to page so [00:40:00] deeply into directory if you C, because they have the same structure, use the same language, they have the same patterns internally.”
- Publisher
- Latent Space
“We want AI to be deployed widely, to do economically valuable work, then we need to find ways for them to naturally collaborate with humans, which means collaboration tooling, I think, is an interesting space to explore.”
- Publisher
- Latent Space
“10 times slower than I would be. But because we paid that cost, we ended up getting to something much more productive than any one engineer could be because we built the tools, the assembly station for the agent to do the whole thing.”
- Publisher
- Latent Space
“Fundamentally, software is made more flexible when it’s able to adapt to the environment in which it is deployed, which means that things like linear or GitHub even are specified within the spec, but not required pieces of it.”
- Publisher
- Latent Space