,
12 tweets,
4 min read
Read on Twitter
Next up: @jessitron on Principles of Collaborative Automation. #devopsdaysnyc
DevOps isn't automation (although automation contributes to it). It is a situation involving people. The principles in this talk come out of the resilience community, who have done a lot of study of collaboration. #devopsdaysnyc
Symathesy - a system that learns made up of parts that are also learning. In DevOps situations, this is a _sociotechnical_ system. We learn from our systems as we experience their behaviors; since we can change our automation, it can also learn from us. #devopsdaysnyc
Joint activities are things we do where we have shared objectives and interdependencies. There are known principles for navigating collaboration when engaged in joint activities. #devopsdaysnyc
The _basic compact_ involves a commitment to noticing failure, communicate them, and correct them. We work this way inside the system, so that the external experience is reliable. #devopsdaysnyc
Being _mutually predictable_ means we need to understand how our collaborators will react to specific signals / events / conditions, and to communicate when we won't meet that expectation. We need to be more precise than "hire people like me." #devopsdaysnyc
As humans, we need to discover _why_ things occur. "The algorithm said so" isn't a valid why. We need to be able to explain and understand, at least in retrospect. Part of this is developing the ability to bring people into context. #devopsdaysnyc
_Mutual directability_ is the ability to influence our collaborators (whether human or technical components of the system). Presenting and explaining choices is better than forcing single options. #devopsdaysnyc
The more flexible actor in an interaction has more power. We need to keep our software directable, keeping the power in the hands of the humans. #devopsdaysnyc
_Common ground_ is the shared context and mental models that form the basis of communication. [I'm reminded of the Gricean maxims for communication.] #devopsdaysnyc
Layers between tech components serve to establish common ground between the actors, including making elements interpretable to humans. #devopsdaysnyc
Key point: Let the human decide things, and let the human see what's going on. #devopsdaysnyc
