Let Humans Human and Computers Computer - LRUG 09/17

A Tale of building useful and effective automations

Transcript

1. Let Humans Human and Computers Computer A Tale of Building Useful and Effective Automations Jan Krutisch <jan@depfu.com> LRUG September 2017
2. Let Humans Human and Computers Computer A Tale of Building Useful and Effective Automations Jan Krutisch <jan@depfu.com> LRUG September 2017
3. Building automations
4. Why automate?
8. Cost
10. work more enjoyable less errors less cost and/or work
11. Downsides
12. #1 Good automations make the easy trivial and the complicated possible
13. Testing
15. Boring
16. Repetitive
17. DŽ Error prone
18. Unit tests
19. Speed
20. ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... ......................................................... .................................................F
21. High level tests
22. Cucumber
23. @javascript
24. CI is asynchronous
25. #2 Good automations integrate into your team workflows
26. Dependency Updates
27. Brief excursion
28. gem push afm-0.2.3.gem depfu/update/afm-0.2.3 Pull Request CI run Merge
29. Pull requests: conversations
30. Information Gathering
31. Screenshot
32. #3 Good automations codify best practices
33. Deployment
35. FTP
36. mysql> UPDATE transactions ADD COLUMN original_value INT...
37. Capistrano
38. Boring
39. Repetitive
40. Error prone
41. Speed
42. Atomic operation
43. Rollback
44. #4 Good automations stay out of the way.
45. Dependency Updates
46.  Nobody wants another inbox!
47.  Cleaning up
48. Close old duplicates
49. Keep noise down
50. ȱ Resepect Limits (of man and machine)
51. #5 Not everything that can be automated should be automated.
52. Continuous deployment
53. Higher risk
54. More complexity
56. Dependency Updates
57. No automatic merge
58. Too little information
59. Higher risk
60. Too high risk
62. More info • John Allspaw on automation part 1, part2 • Courtney Nash's automation myths • Of course: depfu.com Depfu • Me: halfbyte halfbyte <jan@depfu.com> • THANK YOU SO MUCH! ❤ ❤ ❤