“Slack in development teams leaves room for sickness, for onboarding, for helping other teams. It leaves room for checking production to see whether the feature we released last week had any unexpected effects. It lets us do our best work. Resilience comes with healthier systems and healthier people.”
Great Sunday read by @jessitron
https://jessitron.com/2023/01/16/resilience-and-waste-in-software-teams/
@brenden @jessitron @arrjay this is absolutley correct, and ties into something it took literal decades for me to fully understand:
“If it ain’t broke, don’t fix it” is a trap.
It’s the thought process behind so many problems and disasters, and it is an effective trap because it feels right, and humans are creatures of feelings no matter how we lie to ourselves otherwise.
💯
I've been bitten by that trap a couple of times in the last year.
It makes it a much more unpleasant, stressful experience, vs. encouraging stewardship of what you're building and allowing the time to examine the current status of everything.
Definitely! As long as the priority is handled in a way that doesn't mean the team is constantly context switching back and forth between valuable things.
It's a culture thing. And that makes it the hardest thing to change, but the easiest to imagine doing.
SW had really great PR and goodwill. I hope they're using this kick in the pants to get their pivot their attitude to internal systems
Brenden
Bynkii
Urs Enzler 🐉
🖥️ & 🍺
costrike