[LRUG] [Workflow] Getting a Pull Request from creation to merge

David Waller david.a.waller at btinternet.com
Tue Aug 20 11:21:07 PDT 2013


A bit late to add my 2p, but anyway...

Context switching cost is almost impossible to avoid, but I've found that you can mitigate it in small ways
- keep changes small so that they're fast to review
- the team needs a shared commitment to not blocking each other
- a reviewer shouldn't be pulling themselves out of a deep state of 'flow', but there are plenty of times when you're taking a lunch break, catching up on email, etc. when you can tack a code review onto the end.

If you're doing continuous deployment or something along those lines, one of the key benefits is being able to turn round a fix in next to no time.  If maintaining that sort of feature/bugfix velocity is a priority for your team then much of what I've suggested comes simply as a beneficial side effect of that.

David



More information about the Chat mailing list