work share

[isnotafunction]

I know some of you had a tough week so this is just to keep in mind for the future, try to switch pairs (and machines) regularly and make sure everyone has a chance to contribute in a balanced way

[vlbee]

☝️seconding @isnotafunction's comment. Easier said than done sometimes. Some tricks that helped my project teams deal with this:

Pass working branches back and forth between the two people in a pair, so they both get to make commits on the same branch before merges. I noticed you did this on PR #9 🙌

Another trick is to make more commits as you go, or if you prefer to commit at the end, then only stage and commit one file at a time. At this point your pairing buddy could also pull the branch, and you can divvy up which files to commit. This helpful if you both typed but just worked on one computer.

[sima-qian]

So, if you look at my commits, you'll see that four are the first commits initialising the repo, and five are updating the README to get a gif to display.

Furthermore, @EmilyScripts was ill on the first day of the project, so she will likely have fewer commits. It also meant that we worked as a trio on the first day, switching between @sbinlondon's laptop and my own, which resulted in us accruing a number of commits despite not necessarily being the one at the keyboard.

[vlbee]

@sima-qian No worries. 🔥Hot tip for all those README.md commits when you are just fixing a gazillion typos which always happens to me - if you do the README in a separate branch, in the PR you can "squash and merge" your branch commits into one commit for the master. I lurve the squash-merge ☺️