Rain Paharia

And for me, I think there's a way David put it that was really memorable.

A code that uses LLMs extensively had better be the best freaking code on the planet.

If you're doing this, all your code should be extremely tight.

You should put all the work into refactoring, good documentation, all of these things that I think

you know, many of us feel like our, you know, maybe kind of slipped down our priority list.

It is very helpful to think of these tools as not ways to improve the velocity of what you do, but ways to improve the quality of what you do.

And so I'm like, you know, if there's one thing that I think I want people to take away, it is like, slow down, right?

Like, don't just like, you know, spit out as much code as possible.

Instead, like,

use the LLM, right?

Which is a tool there to be like, okay, you know, maybe let's refactor this.

Maybe let's, you know, split this up.

Like there's so many things you can do to improve code quality along the way that will lead you to higher code quality than you would be able to do in the same amount of time.

I mean, for me, it's just like, there are so many things that I feel like I've been able to do with this to increase rigor.

Like my interest, like I've, you know, I've got a couple of things here and there, but like my interest as a professional is really focusing on rigor.

And my background is in dev tools where like correctness is like absolutely essential and non-negotiable.

And for me, it's like, okay, you know, there are so many more tests that I'm writing now.

Like I, you know, the other day I was like,

I want to learn how to use Kani, which is this model checker for Rust.

And I wanted to use that.