Adam Leventhal

Okay, so another question I have for you, because the other thing is that when you are, I mean, as you say, it's, I've got the pattern, I want you to replicate it.

It also makes for a code that's pretty easy for you to review.

This kind of reminds me of my experience.

I pretty much know exactly what I'm expecting here, and I'm going to be able to review this

pretty quickly.

Rain, one question I've got for you, because one thing that was super surprising for me is, and like, look, maybe, hopefully I'm in a safe space here.

Like, I've got the brain that I engage when I'm writing my own software, and I struggle to engage that when I'm reviewing someone else's software.

You know, I try to.

And the best reviewers, I think, are able to review code as if they themselves are writing it.

And I think, but to me, like, I really have to work on that.

And I definitely know when I'm in the like, yeah, yeah, this probably works mode of my brain versus the like, no, no, wait a minute.

Like this, like, I need to like, I'm in like doing my checklist before takeoff and I'm like, I'm going to die in this airplane if I don't get the flaps down correctly.

So I'm like, and the thing that was super surprising to me is that when I was reviewing Claude's work, I was in that mode of like, I'm writing this myself.

and like a heightened state of alert, really reviewing things closely, finding some subtle things in its script.

Did you find the same when you were reviewing the code that it had written?

Yeah, like, oh, by the way, like here, let me show you all the trivial stuff, the non-trivial stuff.

I don't know.

That's a lot of files.

That's a lot of lines to render.

Let's not review that.