David Shu

and you develop a training set that's automatically generated based on translating some existing programs into your language, and you train models for it, you could imagine tweaking the syntax of your new language, regenerating the training set, and then seeing if your benchmarks improve or not.

and you develop a training set that's automatically generated based on translating some existing programs into your language, and you train models for it, you could imagine tweaking the syntax of your new language, regenerating the training set, and then seeing if your benchmarks improve or not.

So you can imagine driving readability of programming languages based on your ability to train an LLM to write this language. And so there's lots of really fun things that will happen long term that I don't think anyone started on work like that yet.

So you can imagine driving readability of programming languages based on your ability to train an LLM to write this language. And so there's lots of really fun things that will happen long term that I don't think anyone started on work like that yet.

Yeah, it's a good question. It's all of the techniques we're applying at General, but they are all very... Each technique requires a lot of Go-specific implementation. So in much the same way that a lot of the techniques inside a language server for a programming language, these are the systems inside VS Code for generating information about programming languages.

Yeah, it's a good question. It's all of the techniques we're applying at General, but they are all very... Each technique requires a lot of Go-specific implementation. So in much the same way that a lot of the techniques inside a language server for a programming language, these are the systems inside VS Code for generating information about programming languages.

The techniques are general for what methods are available on this object. very similar in Go as they would be in Java, for example. But the specifics of implementing them for both languages are radically different. And I think it's a lot like that for Sketch. The tricks we're using for Sketch are very Go specific.

The techniques are general for what methods are available on this object. very similar in Go as they would be in Java, for example. But the specifics of implementing them for both languages are radically different. And I think it's a lot like that for Sketch. The tricks we're using for Sketch are very Go specific.

And if we wanted to build one for Ruby, we would have to build something very, very different. So yes, I consider it very much a Go product right now. And I really like that focus that that gives us. Because Go is a big enough problem on its own, let alone all of programming.

And if we wanted to build one for Ruby, we would have to build something very, very different. So yes, I consider it very much a Go product right now. And I really like that focus that that gives us. Because Go is a big enough problem on its own, let alone all of programming.

I mean, that's a really good question.

I mean, that's a really good question.

Yeah. So I very much admire VS Code. I use it, which I don't actually have to admire a program to use it. That's better than admiring is using, I think. Yeah, that's right. But actually, I do both. I both admire it and use it. But to look at the inside of VS Code, which I've been doing a bunch of recently... VS Code didn't actually solve language servers for all programming languages.

Yeah. So I very much admire VS Code. I use it, which I don't actually have to admire a program to use it. That's better than admiring is using, I think. Yeah, that's right. But actually, I do both. I both admire it and use it. But to look at the inside of VS Code, which I've been doing a bunch of recently... VS Code didn't actually solve language servers for all programming languages.

They built JavaScript and TypeScript, JSON... and I think they maintained the C Sharp plugin. They started the Go plugin, I think, and then it got taken over by the Go team at Google, who now maintain the Go support in VS Code. I don't think the Microsoft team built the Ruby support in VS Code.

They built JavaScript and TypeScript, JSON... and I think they maintained the C Sharp plugin. They started the Go plugin, I think, and then it got taken over by the Go team at Google, who now maintain the Go support in VS Code. I don't think the Microsoft team built the Ruby support in VS Code.

I don't know who did the Python implementation, but a lot of the machinery in VS Code is actually community-maintained for these various programming languages. And so... I'm not sure there is another option than imagining a world where each of these communities supports the tooling in some form. I don't know if each programming language needs to go out and build their own sketch.

I don't know who did the Python implementation, but a lot of the machinery in VS Code is actually community-maintained for these various programming languages. And so... I'm not sure there is another option than imagining a world where each of these communities supports the tooling in some form. I don't know if each programming language needs to go out and build their own sketch.

Maybe there is some generalizable intermediate layer, some equivalent of a language server that can be written to feed underlying models. Given our... We're just starting to explore this space. Sketch is very new. We basically started it sometime near the end of November. So there's not much to it yet. Yeah.

Maybe there is some generalizable intermediate layer, some equivalent of a language server that can be written to feed underlying models. Given our... We're just starting to explore this space. Sketch is very new. We basically started it sometime near the end of November. So there's not much to it yet. Yeah.