High Signal Podcasts Evidence ledger
Method
Browse
← Back to evidence

Evidence receipt / belief

Published · transcript-backed

Simon Willison: belief

10 Jul 2023 Latent Space Code Interpreter == GPT 4.5 (w/ Simon Willison, Alex Volkov, Aravind Srinivas, Alex Graveley, et al.)

“One thing I would say is that if you can upload up to a hundred megabytes, a hundred megabyte file, if you, you can, for most business on six problems, you can get that down to less than a hundred megabytes of data.”

— Simon Willison

Source trail

Everything needed to verify it.

Speaker
Simon Willison
Attribution
Verified speaker
Claim type
belief
Recorded
10 Jul 2023
Publisher
Latent Space

Transcript context

…Yeah. And that could be a very quick intern project at OpenAI. I think. So I wanna get to Gabriel last, and Gabriel has been a great participant in his space, then Kyle then who just came up. And then I think, we'll, we'll give Simon and fix the last words and then we'll close out. Go ahead Gabriel. Yeah, so I think that the killer use case for the code interpreter is basically business analyst. You know, business analyst requires a really deep understanding of the business, you know, user funnel market and really only requires basic, you know, data analysis skills and junior business analysts coming into an organization. And it takes them year, two years to really understand the business and, and, you know, everything associated with it while executives know the business and they're just missing a little bit of the data analysis. I think that's the killer use case. And in order for code interpreter to really seriously be used in that role. I think open AI needs to allow a better way of feeding my data to the model than uploading a file. I think I need to be able to provide an API key and say, here's the endpoint and here's what my data looks like, and you can query my data directly and and analyze it. I think some amount of this they talked about and, and fine tuning something and this would like at least get some way there, right? Like you'd be able to fine tune your own version. So I've built a version of that as a plugin against my, my dataset software and it, you know, so the plugins do give you a way to do that. One thing I would say is that if you can upload up to a hundred megabytes, a hundred megabyte file, if you, you can, for most business on six problems, you can get that down to less than a hundred megabytes of data. Like run a query against your data warehouse, pulling back the highlights of the log file from the past 30 days or whatever. Get that into a hundred megabytes SQLite file or CSV file, upload that into code, do that sort of last mile analysis within it so you can get a surprisingly long way with the tool they've given us already. If you're willing to put a little bit of work into extracting outta 100 megabyte chunk of, of data, that can answer your question. Yeah. Yeah. I, I agree. I think there's a, it can take you pretty far, code interpreter, but it can't really get all the way there because ultimately you're making the decision of what data you're uploading. Whereas when you're attacking a problem you don't know at the beginning what data you actually need and it's kind of this. Trial and error process of trying to figure out what columns and what rows and which table it's in. And if I have to figure all of that out before I start working on the problem, then I'm kind of already locked into, you know, looking at specific things and you, you can't really, you know, just follow the data wherever it takes you. That makes sense, Gabriel, thank you. Kyle, and then, and then we'll close off with folks. Yeah. Yeah. I think so one of the, one of the really interesting ways to look at code interpreter and like just building a top of the other models is that you can still do like a style transfer and you get different styles of code. If you're saying, oh, I want a data engineer or a statistician that would write this, and you get kind of their own interpretation of the code that you're gonna get. Cause you could do the generic prompts and get something really general out. But it's been really fun to get it to do like ETL type work and do EED type work as if those are individual personas that you're working with. Nope. Janae Ade feel free to introduce yourself and plug in our AI meter up real quick. And then, and then tell us what you would like for this code interpreter in the future. Yeah, yeah. So my name's Ade. I'm one of these newcomers. So I started using chat g p T to learn programming at the beginning of the year and actually launched an iOS app that uses the OpenAI api, like right before they switched over to 3.5. I also run the Denver AI tinkerers meetup group. So anybody in the Denver or Colorado area who's listening, feel free to follow me. And check out the the event. We've got one coming up in a couple weeks, so I've only had a chance to play with code interpreter for just a little bit. I didn't actually get access to it until like late last night. I like my, my log out login finally worked in there. It was this morning I fed it a swift file that makes up basically a very simple game that I have. It's just, you know, a frog hops around and eats bugs for 10 levels, but I just fed at the file and said, Hey, look at this and analyze it. Tell me how I can make this game better. And it it did, it, it, it sp sped out, you know, an entire description of really every element of the game. And then made a number of suggestions that, some of which I hadn't even thought of before about how I could go ahead and improve it.…

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

Search evidence