Has anyone worked on a team with no code review culture?

I joined my current company two months ago after switching jobs, but there’s no concept of code review at all. Everyone pushes directly to the main branch, and even when someone opens a PR, it just gets one approval and that’s it.

The problem is that from a new hire’s perspective, there’s no learning, and it’s risky too. You’re supposed to grow by looking at senior engineers’ code, but since everyone just does everything alone, there’s no one to ask when you get stuck.

Is there a way to grow on my own in an environment like this? I’m debating whether I should just leave.

by 알고리즘고수353

10 answers

Agreed—there are surprisingly many places like that these days.

by 알고리즘고수306 · ▲0

Just creating a single PR template can change the vibe quite a bit. Try adding just three fields: reason for change / scope of impact / how to test. There’s little pushback from the team and you’ll see results quickly. Have you tried it?

by 호기심천국213 · ▲0

Well, I think it’s too early to judge after only two months. Why not have the new hire take the lead in gradually building a review culture by asking, “Why did you write this this way?” If there’s someone who’ll at least click approve, just start with that.

by 주말개발자881 · ▲0

Wait—there are people who click approve, right? So doesn’t that mean reviews do exist? “There’s no concept of code review at all” and “it exists only in form” are completely different issues, but the post seems to conflate them a bit. Isn’t the key question what actually gets discussed in PR comments?

by 밤샘코더970 · ▲0

To be blunt, teams with a proper code review culture are in the minority. Expecting growth from your company is a stretch to begin with—these days, you have to create your own growth outside work. Put off switching jobs until the next stage and fill the gap here with personal projects or open source.

by 프롬프트장인451 · ▲0

Start with what you can do right now: ① Leave self-review comments on your own PRs (explaining why you did it this way) ② Break PRs into smaller units ③ When reviewing someone else’s code, leave just one question-style comment like “Why did you do it this way?” If you do just these three things for three months, the team atmosphere will shift a bit. The question-style comments are especially key. Pointing things out makes people defensive, but questions turn into a conversation. Setting up code review tools or creating a convention document comes after that.

by 클라우드러버272 · ▲0

Things to be careful about when proposing a review culture: if you frame it as the whole team being the problem, you'll make enemies right away. Use the “I want to grow” framing, apply it only to your own PRs first, and show that it benefits others when they see it—that's the right order. That's how our team took six months to establish a 30-minute weekly review session. At first, no one showed up lol. But once it caught on, no one skipped it. Don't jump to conclusions—just try it for three months. If you're still frustrated then, it's not too late to move teams at that point.

by 카페인중독200 · ▲0

I was on a team like that for three years. I genuinely learned nothing—instead, I turned to open-source PRs and barely became a functioning person. The conclusion is to change jobs, but before that, so the time you can spend isn’t wasted, I recommend building the habit of getting reviews from open-source communities. Learning how to receive reviews itself is a surprisingly big asset.

by 월급루팡866 · ▲0

I'm in that kind of environment too. Hang in there.

by 문과출신개발자146 · ▲0

You say there’s no senior to ask, but then who’s clicking approve lol

by 밤샘코더382 · ▲0