DevOps for Developer

This talk is about what Developers can do to improve collaboration between Devs and Ops.
Held at code.talks in Hamburg and at IPC/WebTechCon in Munich.

Transcript

1. DEVOPS for DEVELOPERS
2. http://zeroturnaround.com/rebellabs/why-your-organization-hates-devops-and-wont-implement-it-this-year-again/ The real decision makers in the IT world actually loath DevOps, but enjoy publicly supporting it and calling it a priority for „next year“
3. 85% of your financial success is due to your personality and ability to communicate, negotiate, and lead. Shockingly, only 15% is due to technical knowledge. Carnegie Institute of Technology
4. 85% of your financial success is due to your personality and ability to communicate, negotiate, and lead. Shockingly, only 15% is due to technical knowledge. Carnegie Institute of Technology
5. 85% of your financial success is due to your personality and ability to communicate, negotiate, and lead. Shockingly, only 15% is due to technical knowledge. Carnegie Institute of Technology
6. DEVELOPERS
7. OPERATORS
8. DEVOPS
9. LEGAL DISCLAIMER THE FOLLOWING CONTENT REPRESENTS ONLY THE PERSONAL OPINIONS OF THE SPEAKERS AND IS THEREFORE NOT NECESSARILY THE POSITION OF 1&1 INTERNET SE.
10. TIM Adam
11. WHO KNOWS DEVOPS
14. WHAT CAN DEVOPS LEARN FROM Dev OPS Stephen Burton, Tech Evangelist @BurtonSays search for „qcon london 2012 formula“
15. “DevOps is about being agile, and going from A-Ha to Cha Ching as quickly as possible.” John Willis, DevOps Evangelist
16. “DevOps is about being agile, and going from A-Ha to Cha Ching as quickly as possible.” John Willis, DevOps Evangelist
17. de.slideshare.net/appdynamics/what-can-devops-learn-from-formula-1
18. DEVOPS IS ABOUT LEARNING
19. DEVOPS IS ABOUT AGILE
20. DEVOPS IS ABOUT UNDERSTANDING
21. SHARED RESPONSIBILITY (FOR THE PRODUCT)
22. SHARED RESPONSIBILITY (FOR THE PRODUCT) = SHARED KNOWLEDGE (ABOUT THE SYSTEMS)
23. SHARED RESPONSIBILITY (FOR THE PRODUCT) = SHARED KNOWLEDGE (ABOUT THE SYSTEMS) SHARED SUCCESS =
24. WHO IMPLEMENTS DEVOPS
25. 2015 State of DevOps Report 19% devops DEPARTMENTS
26. DEPLOYING CODE TO PRODUCTION
27. SHIP CODE MORE FREQUENTLY 30x 2015 State of DevOps Report
28. OPERATING ON THE WRONG DB
29. FEWER FAILURES 50% 2013 State of DevOps Report
30. FASTER FROM „code committed“ to successfully running code 200x 2015 State of DevOps Report
31. FASTER RECOVERY WHEN INCIDENTS OCCUR 168x 2015 State of DevOps Report
32. Our research shows it doesn't matter how old or new your systems are; high performance can be achieved if the application is architected for testability and deployability. So if you think you can't implement DevOps practices because your app runs on a mainframe, think again. 2015 State of DevOps Report
33. Our research shows it doesn't matter how old or new your systems are; high performance can be achieved if the application is architected for testability and deployability. So if you think you can't implement DevOps practices because your app runs on a mainframe, think again. 2015 State of DevOps Report
34. Saugatuck Technology Inc 52% 37% 29% Y U NO DEVOPS?
35. Saugatuck Technology Inc 52% 37% 29% Y U NO DEVOPS?
36. Saugatuck Technology Inc 52% 37% 29% Overcoming cultural habits LACK OF UNDERSTANDING OF DEVOPS LACK OF BUY-IN FROM LEADERSHIP Y U NO DEVOPS?
37. FROM THE EVERYDAY LIFE
38. „THROW OVER thE FENCE“ CULTURE
39. „THROW OVER thE FENCE“ CULTURE
40. „IT’s a good thing that my staff is sitting in a different building and communicates WITh the dev guys only via tickets.“ Random dinosaur operations manager
41. LEAVE OPS ALONE // punch policy
42. „HIDE THE BUG“ policy
43. FINGERPOINTING CULTURE
44. ORGANIZATIONAL STRUCTURE MATTERS
45. DEVELOPMENT
46. DEVELOPMENT OPERATIONS
47. DEVELOPMENT OPERATIONS QA …
48. DEVELOPMENT OPERATIONS QA … DEVELOPMENT + OPERATIONS + QA + …
49. DEVELOPMENT OPERATIONS QA … DEVELOPMENT + OPERATIONS + QA + …
50. „DEVOPS TEAMS“ WTF
51. „DEVOPS TEAMS“ WTF DEV TEAM OPS TEAM
52. „DEVOPS TEAMS“ WTF DEV TEAM OPS TEAM DEVOPS TEAM
53. I WANT YOU FOR THIS DEVOPS THING
54. 1 YOUR responsibility >>> your code
55. YOUR RESPONSIBILITY >>> YOUR CODE
56. IT’S MORE THAN ONLY TO TAKE THE RESPONSIBILITY ABOUT OWN CODE
58. 2 collaboration at eye level
62. OP DEV
63. OP DEV
64. OP DEV
65. RETROS
70. 3 automation: tests and deployments and even more
71. TESTS
73. DEPLOYMENTS
76. EVEN MORE
79. IMPROVE ALL THE TIME
80. 4 know your PRODUCT
81. NUMBERS
82. NUMBERS
83. NUMBERS
84. NUMBERS
85. NUMBERS
86. 5 culture // talking >>> ticket
88. Das BFH-Urteil vom 16. 6. 2015 lässt sich wie folgt zusammenfassen: (1) Die Ortsregelung des § 3 Abs. 8 UStG ist auch dann anwendbar, wenn keine Einfuhrumsatzsteuer anfällt, weil die Einfuhr umsatzsteuerfrei ist. (2) Eine wirksame direkte Vertretung i. S. des Art. 5 Abs. 2 erster Spiegelstrich ZK setzt voraus, dass der Vertreter für fremde Rechnung handelt. Hieran fehlt es, wenn der Vertreter im Innenverhältnis für alle im Zusammenhang mit der Einfuhr stehenden Zölle, Steuern und Gebühren aufkommt und den Vertretenen insoweit von allen Verpflichtungen befreit. (3) Mit der Annahme einer Zollanmeldung für die Überführung der Ware in den freien Verkehr entsteht die Einfuhrumsatzsteuer. (4) Ein Missbrauch von Gestaltungsmöglichkeiten des Rechts i. S. des § 42 AO kommt auf dem Gebiet der Umsatzsteuer in Betracht, wenn zum einen die in Rede stehenden Umsätze trotz formaler Anwendung der Bedingungen der einschlägigen Bestimmungen des Unionsrechts und des zu ihrer Umsetzung erlassenen nationalen Rechts einen Steuervorteil zum Ergebnis haben, dessen Gewährung dem mit diesen Bestimmungen verfolgten Ziel zuwiderliefe, und zum anderen aus einer Reihe objektiver Anhaltspunkte ersichtlich ist, dass mit den fraglichen Umsätzen im Wesentlichen ein Steuervorteil bezweckt wird.
91. TL;DR
92. 1 YOUR responsibility >>> your code
93. 1 YOUR responsibility >>> your code 2 collaboration at eye level
94. 1 YOUR responsibility >>> your code 2 collaboration at eye level 3 automation
95. 1 YOUR responsibility >>> your code 2 collaboration at eye level 3 automation 4 know your PRODUCT
96. 1 YOUR responsibility >>> your code 2 collaboration at eye level 3 automation 4 know your PRODUCT 5 culture
97. THANKS! QUESTIONS?
98. www.competence.wtf @schuppi @urbanisierung THANKS! QUESTIONS?