* Seven Basic Tools of Quality – Cause-and-effect diagram, Check sheet, Control chart, Histogram, Pareto chart, Scatter diagram, Stratification (alternately, flow chart or run chart)
* Successful Workshops – a Mindmap by Ash Winter
Ansible is not about commands, it’s about states. So it will make sure path x is empty, or file x is in place y, but it doesn’t care whether it has to do something for this.
- Troy Hunt: Speaker style bingo: 10 presentation anti-patterns
Identifies common speaker types representing anti-patterns like The Bullet Pointer or The Apologist, while giving example checklists and good practices.
- Karo Stoltzenburg: PechaKucha: Now you see it – now you don’t
Reflections on what works better and what works less when presenting, from example presentations in the PechaKucha format (20 images, each shown for exactly 20 seconds).
Growing and unordered list of books that I’m coming across being referenced as worth wile reads for Testers:
- Perfect Software, and Other Illusions about Testing by Gerald Weinberg (2011)
- Explore It! by Elizabeth Hendrickson (2014)
- The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win by
- 50 quick ideas to improve your tests by Gojko Adzic, David Evans, Tom Roden (2015)
# http://ryanstutorials.net/linuxtutorial/ -> Some general house rules
- <something> usually means that you are to replace this with something useful. If you see something such as <n> then it usually means replace this with a number.
- [something] usually means that this something is optional. When you run the command you may put in the something or leave it out.