Post #1814334
2026-04-27 04:07 UTC
Replies (2)
-
@dtauvdiodr@c.im 2026-04-27 04:49
@norootcause I'd say we do have the ability to focus on adaptation outside of incidents if we practice. When we practice together we are surfacing our regular work, the stuff we do that creates safety. That builds connections and pathways for adaptive capacity to become connected.
-
@tiotasram@kolektiva.social 2026-04-28 09:28
@norootcause very interesting! I'm not nearly any kind of expert on this stuff, but recently in thinking about my own behavior (specifically: time spent rewriting documentation to fix overlapping terminology) I realized that in order to explain the value of the work, I had to shift from thinking about "how does this contribute to a working product" to "how does this contribute to a developer ecosystem which continues to work on the product?" Viewing the dev team as a system which is self-perpetuating (or not) and understanding that as long as you can self-perpetuate a dev team which makes meaningful progress in the project it will eventually get done. Even with a team of 1 (I'm almost exclusively a solo dev these days) this still makes sense, as one can think about how various choices influence your own continuation desire & capability. I feel like this shift from measuring the state of the software to measuring the state of the team might jive with Safety II. You'd ask questions like "what factors/events are causing our devs to depersist, either in total or from touching parts of the software that may end up neglected?" as well as "what motivates the team to continue their work (including but beyond the paycheck)?" For open-source/volunteer/hobby projects in particular (which I'm most interested in) this is a very interesting question, especially as you need to ask how new volunteers are welcomed and cultivated.