200313

Sometimes collaboration just goes perfectly, and it's a happy experience to be part of it.

Issue #313 is one example of such collaboration:

• a problem was reported
• asynchronous discussion happened (engineers received @-notifications and added comments when it was convenient for them)
• solutions were proposed
• a workaround was written, commented on, documented
• finally, a simple solution was discovered and merged

Participants: 5
Patches: 2
Meetings: 0

Another example is the "M4 & hac[k]ing session". Most meetings are toxic. This one was a rare exception.

Engineers: 3
Meetings: 1
Drawings: 1
Emails: 1

What I liked about those two cases is that we worked in synchrony. When one stopped (or went offline), the partner stepped in. With no domination. It felt like a dance.

It feels good to be a redundant contributor. (The phrase sounds very HA. Is there social HA? 🙂)

redundant
adjective

[...]

• Engineering (of a component) not strictly necessary to functioning but included in case of failure in another component: the modules are linked using a redundant fibre-optic cable.

-- @vvv