mydreamof23 minutes ago
IMO it depends on the company. If everyone in the company has to provide a lot of PRS etc. you have to stop care about the quality and just get the paycheck. The CEO decided not you. (Of course not when the product may charm ppl etc.)
newsomix9xl5 hours ago
I always use AI to understand big diffs.
And you can always reject a PR, bro with "I don't understand it to approve it. Maybe make it smaller or documents it better?" Etc
I've had code approvers who gave me tons of crap, even over smaller edits. You too can be that kind of reviewer!
nasretdinov34 minutes ago
Yeah that's quite odd that people somehow now think you can't reject a PR because you can't understand it -- but initially that was one of the reasons to have code review in the first place.
DarmokTanagra24 minutes ago
Do it enough and you become the problem.
I ran into this at my previous company and ended up getting scolded for being a bottleneck when I was just sending back AI slop code.
jdw643 hours ago
Personally, one thing I like about Claude is that before, specifications kept changing through verbal explanations. Now, with Claude, everything is communicated in writing, so there's no room for shifting blame.
Does this kind of difference vary depending on the engineering organization?