[mdekkers]

I spend a disproportionate amount of time on PRs at $client and recently got dinged for not performing “enough” so I stopped reviewing PRs.

PRs have dwell times of weeks. It’s all broken, but somehow we are all convinced that this is better than a formalised change review process.

Never mind the inability to plan work, or having to have yet another discussion with some corporate random that happens to be reviewing your PR and has a thousand questions as to why this particular functionality needs to be implemented, and why weren’t they consulted - dude, here is all the process documentation, go complain at management, not me.

But in the meantime, management wants to know why x was not delivered on time.

[xorcist]

Teamwork takes time. I think a lot of people do not understand that.

As soon as we get above two or three tightly knit people internal communication starts to become the bottleneck. It's inherently serialized. It's the human equivalent of Amdahl's law.

Never has it been more clear than when remote work took over in organization that are not built on it from the start. While we all feel more productive without office chit chat it all has to be compensated somehow if we're going to be aligned with common goals.

Perhaps we need to dedicate 25% work time to PR's. It's just half of what pair programming is and plenty of people are productive doing that.