Andrej Karpathy

I think these models are good in certain parts of the stack.

I actually use the models a little bit in... There are two examples where I actually use the models that I think are illustrative.

One was when I generated the report.

That's actually more boilerplate-y.

So I actually bytecoded partially some of that stuff.

That was fine.

Because it's not like mission-critical stuff and it works fine.

And then the other part is when I was rewriting the tokenizer in Rust...

I'm actually not as good at Rust because I'm fairly new to Rust.

So I was doing, there's a bit of vibe coding going on when I was writing some of the Rust code.

But I had Python implementation that I fully understand and I'm just making sure I'm making a more efficient version of it and I have tests.

So I feel safer doing that stuff.

And so basically they lower or like they increase accessibility to languages or paradigms that you might not be as familiar with.

So I think they're very helpful there as well.

Yeah.

Because there's a ton of Rust code out there.

The models are actually pretty good at it.

I happen to not know that much about it.

So the models are very useful there.

And I think you're getting at some of my, like why my timelines are a bit longer.