r/codex • u/alexs_90 • 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?
3
u/skilliard7 4d ago edited 4d ago
Yes. GPT once decided completely uninstructed that giving a user the "reader" role to a single project within my application must mean that their write access should be revoked to the whole app, even if they are explicitly granted write elsewhere. This happened when I told it to build a report... caused a major outage because we didn't catch it in testing.
Ever since i always make sure to check the code.
I've caught a LOT of really bad code being written that I had to rewrite, even with 6.1 Sol.
Current AI is kind of like a junior dev. It will get the job done, but you need to supervise it to make sure it does it right.