laurens/fediversity_website
Archived
2
1
Fork 1
Code Issues Pull requests Packages Projects Releases Wiki Activity

Markdown aanpassing. Escape van bepaalde karakters die wegvallen uit het abstract

Browse source
This commit is contained in:
Patrick Reijnen 2023-08-12 17:10:18 +02:00
parent aad18dbf4f
commit 503a4ad4da
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/evenementen/nluug/najaarsconferentie-2018/talks/mike-ciavarella-shaved-yaks-saving-an-endangered-species.md
View file

@ -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?!? 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 <insert favorite battle-tested tool here />”. _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 \<insert favorite battle-tested tool here /\>”. _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. This talk is about the decisions and assumptions behind automation, and, perhaps, why yak shaving needs to be preserved.