David Shu

I mean, I totally agree that it is coming for it. I also think it's very early days and a great reason to not learn this technology today. is that it's changing so fast. Yeah. And that you can spend a very long time figuring out how to make it work, and then all of that accumulated skill can be sort of made useless tomorrow by some new product.

I mean, I totally agree that it is coming for it. I also think it's very early days and a great reason to not learn this technology today. is that it's changing so fast. Yeah. And that you can spend a very long time figuring out how to make it work, and then all of that accumulated skill can be sort of made useless tomorrow by some new product.

Yeah.

Yeah.

Yeah, absolutely. Like a year ago, a common technique with open models that existed was to offer them money to solve problems. You start every prompt by saying, I'll give you $200 if you do this. And it greatly improved outcomes.

Yeah, absolutely. Like a year ago, a common technique with open models that existed was to offer them money to solve problems. You start every prompt by saying, I'll give you $200 if you do this. And it greatly improved outcomes.

All of those techniques are gone now. Yeah. Like if you try bribing a model, it doesn't help. Yeah. There was a great example I saw of that where someone kept saying, I'll give you $200 if you do this. And they did it in a single prompt several times. And they got to the nth case and it said, but you haven't paid me for the previous ones yet.

All of those techniques are gone now. Yeah. Like if you try bribing a model, it doesn't help. Yeah. There was a great example I saw of that where someone kept saying, I'll give you $200 if you do this. And they did it in a single prompt several times. And they got to the nth case and it said, but you haven't paid me for the previous ones yet.

No means no. That's great. No money means no. Yeah, there you go. All right. They're very funny models. So I spent a long time believing, and I actually, I still believe this in the long term, that chat,

No means no. That's great. No money means no. Yeah, there you go. All right. They're very funny models. So I spent a long time believing, and I actually, I still believe this in the long term, that chat,

is our is currently our primary user interface on the models and it's not the best interface for most things the way to get the most value out of models today when you program is to have conversations with models about what you're writing and that's i i think it's it's quite the mode shift to do that it's quite taxing to do that and it feels like uh

is our is currently our primary user interface on the models and it's not the best interface for most things the way to get the most value out of models today when you program is to have conversations with models about what you're writing and that's i i think it's it's quite the mode shift to do that it's quite taxing to do that and it feels like uh

it feels like a user interface problem that hasn't been solved yet and so uh i've been working a lot with uh josh bleacher snyder on these things uh and we uh have been sort of we spent a long time looking for how can we avoid the chat paradigm and make use of models that's why code completion initially was so interesting because it's an example of using models without chat and it's very effective

it feels like a user interface problem that hasn't been solved yet and so uh i've been working a lot with uh josh bleacher snyder on these things uh and we uh have been sort of we spent a long time looking for how can we avoid the chat paradigm and make use of models that's why code completion initially was so interesting because it's an example of using models without chat and it's very effective

So we spent a long time exploring this. To give you another example of something we built in this space, because we've just been trying to build things to see what's actually useful, we built something called Merd, merd.ai, which I think we put up a few weeks ago. And it does merge commits for you. So if you try and push a git commit or do a rebase and you get a merge conflict,

So we spent a long time exploring this. To give you another example of something we built in this space, because we've just been trying to build things to see what's actually useful, we built something called Merd, merd.ai, which I think we put up a few weeks ago. And it does merge commits for you. So if you try and push a git commit or do a rebase and you get a merge conflict,

you can actually use LLMs to generate sophisticated merge commits for you. It turns out that's a much harder problem than it looks. Like you would think you just paste in all of the files to the prompt and you ask it to generate the correct files for you. Even the frontier models are all really bad at this. You almost never get a good merge commit out of them.

you can actually use LLMs to generate sophisticated merge commits for you. It turns out that's a much harder problem than it looks. Like you would think you just paste in all of the files to the prompt and you ask it to generate the correct files for you. Even the frontier models are all really bad at this. You almost never get a good merge commit out of them.

But with a whole stack of really mundane engineering out the front, Mundane's not the right word because a lot of it's actually really very sophisticated. But it doesn't involve the LLM itself. It's about carefully constructing the prompt. Traditional is a much better word. You can actually get very good merge commits out of it.

But with a whole stack of really mundane engineering out the front, Mundane's not the right word because a lot of it's actually really very sophisticated. But it doesn't involve the LLM itself. It's about carefully constructing the prompt. Traditional is a much better word. You can actually get very good merge commits out of it.