> The idea of taking weds thru friday basically off to loaf and surf the internet while you wait for other threads on your project to get back to you will hopefully die.
I don't like sitting around waiting for PR feedback, and will typically find other ways to be productive when this happens, but I'm unclear what you expect people to do in this situation.
If you have some code that needs to be reviewed, and the available reviewers aren't reviewing it after you requested their review, then you have three options:
- Remind them. Always a good idea, but you can only do it so often. Sending someone daily reminders over a non-urgent PR is a great way to get your PRs reviewed even more slowly next time. Also, once you're senior or above, your reviewers tend to be busy. You can't wave a magic wand and clear their calendars.
- Escalate to your manager. May or may not be effective. Will make you unpopular if you do it too often, especially if the two of you have the same manager.
- Escalate to their manager. May or may not be effective, but you just irrevocably burned your bridges with that person, hope it was worth it.
And this is just for code review. If QA is involved then you have a whole other layer of bureaucracy to deal with, except with a different reporting chain.
There's a reason engineers at large companies seem so unproductive and it often has nothing to do with their work ethic.