Paul Dix

you know, a lot of times like people are, it's just like, people are just hitting okay or whatever, or they're reviewing it for like stupid, like syntax stuff or whatever.

It's not actually like reviewing the big picture of like, does this actually do what we want it to do?

Not everyone, but like at some point, like sometimes, yeah, even for me, like not all my code reviews are great.

Like some of my code reviews, I'm just like, it's on this day.

I'm just like, ah, let's just get this through.

yeah you know have you ever seen the meme where it's like you submit like a 10 line change and like 100 nitpicks on your code review and then you submit like a 3 000 line edition and it's like lgtm you know merging wave it through yeah exactly i get that i think there's some truth to that uh yeah i mean i i i think it's it's tricky because like for better or worse like software engineering is changing and i think people are just gonna have to like

deal with that.

I think for people who was, somebody wrote this the other day, it's like for people who are like, maybe it's Andre Karpathy.

It's just like for people who, you know, fancy that, who always loved software engineering because they like,

to build things, those people are fine.

But for people who like software engineering, because they like the details of writing code, those people are kind of hosed because, you know, those days are, are, are limited at best.

you can create it.

And when you toss it up for code review or whatever, like people don't nitpick it because the stakes are lower, right?

They're just like, ah, it's internal.

It's not going to go out to a customer.

That's true.

You know?

So the, the problem is when you raise the stakes, when it's like going out to a customer and you really have to worry about it, then it becomes harder to ship.

Right.

And then the, then like your enthusiasm goes,