For Agility's Sake

Building resiliency through safeguarding - Llewellyn Falco

February 03, 2020 Kyle Spitzley / Llewellyn Falco Season 2 Episode 3
Building resiliency through safeguarding - Llewellyn Falco
For Agility's Sake
More Info
For Agility's Sake
Building resiliency through safeguarding - Llewellyn Falco
Feb 03, 2020 Season 2 Episode 3
Kyle Spitzley / Llewellyn Falco

He's back! Tech Craftsmanship Coach Llewellyn Falco shares stories of his second visit to Amway. Some of the topics he touches on in this episode are:

  • Anti-fragile: a systemic way of implementing things so that when they break, you get stronger. More resilient. If your system is dependent on discipline, it’s broken.
  • Safeguarding: after an issue was resolved, the team reflected on these 3 questions to help them build more resiliency for the future: 
    1. What allowed us to create this situation?
    2. What made it hard for us to discover what it was?
    3. What made it hard to fix?
    4. PS: Don't start safeguarding in the middle of a crisis; wait until it's over (but not too long). 
  • Learning through documenting: As you document something, it prompts new ideas for how the thing could work. 
  • Shared, isolated, mutable and non-mutable states: the only combination to avoid is the one that everybody chooses = shared + mutable. 
  • What the team did when multi-threading threw a wrench in their testing…
  • Continuous improvement: stop worrying about how to improve faster, worry about starting. Make improvement an everyday habit, and speed will come later. 
Show Notes

He's back! Tech Craftsmanship Coach Llewellyn Falco shares stories of his second visit to Amway. Some of the topics he touches on in this episode are:

  • Anti-fragile: a systemic way of implementing things so that when they break, you get stronger. More resilient. If your system is dependent on discipline, it’s broken.
  • Safeguarding: after an issue was resolved, the team reflected on these 3 questions to help them build more resiliency for the future: 
    1. What allowed us to create this situation?
    2. What made it hard for us to discover what it was?
    3. What made it hard to fix?
    4. PS: Don't start safeguarding in the middle of a crisis; wait until it's over (but not too long). 
  • Learning through documenting: As you document something, it prompts new ideas for how the thing could work. 
  • Shared, isolated, mutable and non-mutable states: the only combination to avoid is the one that everybody chooses = shared + mutable. 
  • What the team did when multi-threading threw a wrench in their testing…
  • Continuous improvement: stop worrying about how to improve faster, worry about starting. Make improvement an everyday habit, and speed will come later.