4 ms·
Re: 1, pull requests should not be blocking; if it is blocking, go for pair programming instead and/or in addition to. If a pull request not being merged blocks
by Cthulhu_ 7y ago
Re: 1, pull requests should not be blocking; if it is blocking, go for pair programming instead and/or in addition to. If a pull request not being merged blocks someone else then you need to review your planning.
2. Yes, but it should interrupt the whole team. Share the pain, the cause, the solution, and work on how to prevent it in the future.
3. If you're immediately working with them you should be in the same room with them. Or voice comms if you're in a remote situation, but I suspect most people working remote will work quite insulated anyway.
4. Yes.
5. If it's a message it can wait, messages are asynchronous communications. If it's time critical they need to call.
- afarrell 7y ago> it should interrupt the whole team No, it should interrupt the team which owns that area of the codebase. If you're having an issue due to Postgres indexing, what value is there in pulling someone away from writing React.js hooks? If your answer is "By making it painful, you force the problem to get solved." that is incorrect for the same reason that "If you throw a person into a 10-meter-deep lake, you force them to swim" is incorrect.