Ask HN: What to do if coworkers aren't reviewing my code?
I&#x27;m a veteran programmer -- not a 10x genius, but reliable and attentive.<p>My problem is that at my company, a nonprofit, there&#x27;s a culture of not prioritizing reviewing others&#x27; code. That means my code, sometimes even urgent fixes to significant problems, can sit for a week or two before it&#x27;s reviewed. Less urgent changes that should take a day or two of back and forth work and communication instead can many times that.<p>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!<p>The director of engineering tries to help by reviewing code himself, but he&#x27;s overburdened and usually can&#x27;t.<p>What&#x27;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.<p>It&#x27;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.<p>I can&#x27;t say my code is sparklingly perfect, but I don&#x27;t have any reason to think it&#x27;s particularly hard to review or unpleasant to review. My sense is that other people face the same situation, but don&#x27;t mind so much. I know I produce more PRs than other people, and that I have higher expectations for our team productivity.<p>I&#x27;ve brought this up gently many times, but no one else seems to take it seriously. I also frequently offer to review others&#x27; PRs, and make sure to do a thorough and supportive job when I do.<p>What should I do? Keep trying to communicate about how this isn&#x27;t working for me, and I think, for the organization? Try phrasing my needs differently? Look for another job?