Adam Leventhal

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.

Too big.

Why bother?

Yeah, interesting.

So in this first use case, I've got a lot of just tedium that needs to be done.

And the other thing that I think is really interesting about this case is you're doing something that we do a lot, which is like, okay, I've got this problem.

I kind of want to solve it in a way that's a little more generic where my colleagues can use it and so on.