From 503a4ad4da6941d8b518e22775c61ee6f981f520 Mon Sep 17 00:00:00 2001 From: Patrick Reijnen Date: Sat, 12 Aug 2023 17:10:18 +0200 Subject: [PATCH] Markdown aanpassing. Escape van bepaalde karakters die wegvallen uit het abstract --- .../mike-ciavarella-shaved-yaks-saving-an-endangered-species.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/evenementen/nluug/najaarsconferentie-2018/talks/mike-ciavarella-shaved-yaks-saving-an-endangered-species.md b/content/evenementen/nluug/najaarsconferentie-2018/talks/mike-ciavarella-shaved-yaks-saving-an-endangered-species.md index 7a1a2f0..b9afc9d 100644 --- a/content/evenementen/nluug/najaarsconferentie-2018/talks/mike-ciavarella-shaved-yaks-saving-an-endangered-species.md +++ b/content/evenementen/nluug/najaarsconferentie-2018/talks/mike-ciavarella-shaved-yaks-saving-an-endangered-species.md @@ -21,7 +21,7 @@ recording: Automation is meant to make our lives simpler: just throw a shell script at some problem and the problem goes away, right? If only life in a modern DevOps world was so easy! Instead, we have thousands of tools to choose from, and hundreds of problems to solve, even in small environments. Life wasn't meant to be easy, but does it have to have so many command line arguments?!? -Many of the decisions we make regarding automation are based on some combination of “experience”, “that's how it's always been”, and “I just need it to work”. This is not helpful when you have little experience, a green-field site, or even less time available than you thought. Even with experience, we tend to fall back to “Just use ”. _We choose the tool not because it's the right tool for the job, but because it's a tool we know_. This becomes further “justified” on the grounds of personal productivity. Suddenly, tool choice is the important decision, and the original problem is secondary. How can we do better? +Many of the decisions we make regarding automation are based on some combination of “experience”, “that's how it's always been”, and “I just need it to work”. This is not helpful when you have little experience, a green-field site, or even less time available than you thought. Even with experience, we tend to fall back to “Just use \”. _We choose the tool not because it's the right tool for the job, but because it's a tool we know_. This becomes further “justified” on the grounds of personal productivity. Suddenly, tool choice is the important decision, and the original problem is secondary. How can we do better? This talk is about the decisions and assumptions behind automation, and, perhaps, why yak shaving needs to be preserved.