Speakers in the public record
Claim mix
evaluation 3prediction 2belief 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.
6 published records
“the GitHub API because it's way more successful at doing that. So maybe, you know, every website is going to need to have [00:28:00] an API because we're going to be having agents interact with them.”
- Speaker
- Not verified from transcript
- Publisher
- Latent Space
“We don't have a good way to [00:44:00] index into it because like rag, Okay. At least in my experience, RAG from language to code doesn't work super well.”
- Speaker
- Not verified from transcript
- Publisher
- Latent Space
“Very recently we implemented this. And the reason why is because if you want to interact with full websites you will need to click on all of the elements or have the ability to click on all of the elements.”
- Speaker
- Not verified from transcript
- Publisher
- Latent Space
“The first way is the simplest way and the newest way, but it doesn't work very well, which is you take a screenshot of the website and then you click on a particular pixel value on the website.”
- Speaker
- Not verified from transcript
- Publisher
- Latent Space
“I've gotten a bit better at prompting also, so like, just to give an example it, it will sometimes fail to fix a GitHub workflow because it will not look at the GitHub workflow and understand what the GitHub workflow is doing before it solves the problem.”
- Speaker
- Not verified from transcript
- Publisher
- Latent Space
“I think for GitHub, maybe [00:47:00] just pushing this like a little bit more is the way to do this.”
- Speaker
- Not verified from transcript
- Publisher
- Latent Space