My problem is that at my company, a nonprofit, there's a culture of not prioritizing reviewing others' code. That means my code, sometimes even urgent fixes to significant problems, can sit for a week or two before it's reviewed. Less urgent changes that should take a day or two of back and forth work and communication instead can many times that.
When I get assigned code to review, I make it a priority and try not to let more than a day go by without my at least responding with questions. This just makes sense to me -- after all, somebody is waiting on me to merge an improvement to the product!
The director of engineering tries to help by reviewing code himself, but he's overburdened and usually can't.
What's worse, there are fellow engineers I no longer feel comfortable being paired with on projects because the projects are sure to take far too long.
It's exhausting to be constantly spinning my wheels, trying to keep the context of my 6-8 open, unreviewed PRs fresh in my mind so I can move forward with my work.
I can't say my code is sparklingly perfect, but I don't have any reason to think it's particularly hard to review or unpleasant to review. My sense is that other people face the same situation, but don't mind so much. I know I produce more PRs than other people, and that I have higher expectations for our team productivity.
I've brought this up gently many times, but no one else seems to take it seriously. I also frequently offer to review others' PRs, and make sure to do a thorough and supportive job when I do.
What should I do? Keep trying to communicate about how this isn't working for me, and I think, for the organization? Try phrasing my needs differently? Look for another job?
