Sep 19, 2026 · 16 min · 9 segments
Have you ever had someone review your pull request, make changes without telling you, and just merge it in? In the latest episode of the No Compromises podcast, we discuss whether the traditional…
We've done other podcasts where we talk about the importance of code review.
I really like it too, because it's how I can kind of say like to Joel or someone else on my team, this is the work I've done.
Can you take a look at it and see if there's any issues to fix? Or did I make any bugs? Is there any code standards, stuff like that? And I think we talked about that and we made a good point that that's important and that's something I don't ever want to get rid of.
However, I was working with another client the other day.
I thought this was a one-off, and it turns out it might be a pattern, so it's something I want to talk to you about, Joel.
Okay.
So I was working with this other client, and I put a pull request out there, and they took a look at it.
And mind you, this particular work was a while coming, so it was like maybe two or three weeks ago.
The PR had been there for a while, too, and it was like 110 files.
So it was just like, it was sort of a weird sort of scenario, too, where I was starting to forget what I had done on it, and it was sort of languishing.
Well, the other developer was the one who was going to review it, took it, reviewed it, made five or six changes, five or six commits to it, and then just merged it in.
Like, without talking to you? Yeah, without talking to me,
yeah.
Okay.
And I was like...
I don't think that's the point of the code review, right? I thought the code review was to tell me, hey, you know, here's an issue and you can fix it and learn from it.
But before you agree with that, let me put a pin in it because I want to talk about something that happened today with me and Joel.
So with me and you, I guess.
You have another Joel in your life? What's going on here?
We've done other podcasts where we talk about the importance of code review.
I really like it too, because it's how I can kind of say like to Joel or someone else on my team, this is the work I've done.
Can you take a look at it and see if there's any issues to fix? Or did I make any bugs? Is there any code standards, stuff like that? And I think we talked about that and we made a good point that that's important and that's something I don't ever want to get rid of.
However, I was working with another client the other day.
I thought this was a one-off, and it turns out it might be a pattern, so it's something I want to talk to you about, Joel.
Okay.
So I was working with this other client, and I put a pull request out there, and they took a look at it.
And mind you, this particular work was a while coming, so it was like maybe two or three weeks ago.
The PR had been there for a while, too, and it was like 110 files.
So it was just like, it was sort of a weird sort of scenario, too, where I was starting to forget what I had done on it, and it was sort of languishing.
Well, the other developer was the one who was going to review it, took it, reviewed it, made five or six changes, five or six commits to it, and then just merged it in.
Like, without talking to you? Yeah, without talking to me,
yeah.
Okay.
And I was like...
I don't think that's the point of the code review, right? I thought the code review was to tell me, hey, you know, here's an issue and you can fix it and learn from it.
But before you agree with that, let me put a pin in it because I want to talk about something that happened today with me and Joel.
So with me and you, I guess.
You have another Joel in your life? What's going on here?
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.
