Monday, 1 August 2016

Damo's Podcast Highlights 2016 #30

I subscribe to many podcasts, you can see the list as it was in 2015 here: Developer podcasts v2 but I thought I would start to keep a weekly log of the episodes that I found interesting or useful in some way.

[The Cognicast] Michael Nygard - The new normal, failure is a good thing
Blog series the new normal
  • "What we need is a new approach where “continuous partial failure” is the normal state of affairs"
  • "Instead of expecting everything to run like clockwork, we should anticipate the opposite. We must embrace failure as a means to build IT infrastructures and organizations that not only withstand threats but profit from them."
  • Everything breaks. It's just a question of when and how badly.

[Scrum Master Toolbox Podcast] Yves Hanoulle - How systems influence individual and team performance

[This Agile Life] You Can’t Handle the Truth
  • Constructive criticism as a gift
  • How have we (the hosts) established safety (trust) on teams?
  • Can we have trust without transparency?
  • Can we have safety without trust?

[This Agile Life] The Version One 10th Annual State of Agile™ report
The team discuss the bottom 10 of the agile techniques employed on page 10 of the 'Version One 10th Annual State of Agile™ report'
Can you be 'Agile' with out TDD, BDD, refactoring, and pairing?

[AudioBookPodcast.Microservices] Daniel Bryant - The Seven Deadly Sins of Microservices
  1. LUST – Using the latest and greatest tech…
  2. GLUTTONY – Excessive communication protocols
  3. GREED – All your service are belong to us…
  4. SLOTH – Creating a distributed monolith
  5. WRATH – Blowing up when bad things happen
  6. ENVY – The shared single domain fallacy
  7. PRIDE – Testing in the world of transience

[Mastering Business Analysis] Addressing Bottlenecks with Theory of Constraints
The Theory of Constraints is an approach to improving organizational performance created by Dr. Eli Goldratt and is explained in his book, The Goal.
  • Step 0: Define the Goal
  • Step 1: Identify the Bottleneck
  • Step 2: Exploit the Bottleneck
  • Step 3: Subordinate Decisions to the Bottleneck
  • Step 4: Elevate the Bottleneck
  • Step 5: Repeat

No comments:

Post a Comment