One is tight coupling, or lack of slack. “If something goes wrong, you won’t have much time to figure out what’s happening and make adjustments.”
Parts “interact in hidden and unexpected ways.”
Old dams, people could go see what the gate was doing. Now operators in control rooms are “removed from having direct access to the system.”
All software has this quality, because it runs in digital space.
It operates at out of view and at faster time scales than humans naturally work.
And yet, we can make it observable!
If we try super hard.
“A simple punitive approach is an impediment to learning.”
Separate work on safety from rule enforcement. Ya gotta “consider how the rules themselves contribute to accidents.”
But keep an eye on it. Maybe sacrifice some efficiency to get some slack, slow down the rollout to loosen coupling while you learn.
But in complexity, “diversity helps because it makes everyone on a team slightly less comfortable - and as a result, more skeptical.”
#disfluency
“The definition of the problem is a hypothesis to be tested.”