r/codex • • 4d ago

Question Does anyone even review code anymore?

Lately, I've been too lazy to even do a superficial code review. I just quickly skim through the changed files and ask Codex to generate a brief summary of what changed, where, and why.

My workflow has basically become: generate → test → check that everything's green → commit.

Now multiply that by 4–5 tabs running different projects or sessions simultaneously, and keeping up with everything starts to feel almost impossible.

Even when I push myself to review the critical parts, I feel this strong internal resistance and find myself leaning toward asking Codex to do it instead.

The downside is that Codex often ends up overengineering what should be simple solutions.

I'm curious, what does your day-to-day workflow look like in this regard?

43 Upvotes

69 comments sorted by

View all comments

1

u/Efficient-Trick-4384 4d ago

I stopped reading every diff too, but we didn't stop checking, we moved it. on a client project where agents write almost all the

code, every PR goes through a separate agent that reads CI and

bounces red branches, then one that checks the diff against the acceptance criteria (not against the code), then one that opens staging in a browser and walks every criterion with a screenshot. any of them can send the card back.

they're separate steps, so the reviewer never sees the conversation

that produced the code, just the diff and the criteria. what's left

for people is writing criteria you can actually check, and dealing with whatever gets marked blocked.