|
1 | | -+++ |
2 | | -City = "Zurich" |
3 | | -Year = "2025" |
4 | | -talk_date = "2025-03-13" |
5 | | -talk_start_time = "14:25" |
6 | | -talk_end_time = "14:30" |
7 | | -title = "How I Started Worrying and Stopped Loving DevOps" |
8 | | -type = "talk" |
9 | | -speakers = ["marcel-britsch"] |
10 | | -youtube = "" |
11 | | -vimeo = "" |
12 | | -speakerdeck = "" |
13 | | -slideshare = "" |
14 | | -slides = "" |
15 | | -+++ |
16 | | - |
17 | | -### Ignite |
18 | | - |
19 | | -Summary: |
20 | | -In this cautionary tale, I’ll share three real-world product-building experiences, mapping my journey as a product manager from a DevOps enthusiast to a wary cynic. I’ll share examples of how infrastructure can drift into ‘purgatory’: pipelines that are ‘never done,’ painfully complex to maintain, or beautifully engineered yet devoid of applications to support. My goal is to highlight the missteps I encountered, so future teams might avoid these traps and sidestep the costly pursuit of infrastructure perfection that can derail real progress. |
21 | | - |
22 | | -How the talk will unfold: |
23 | | -Introduction: The Allure of DevOps |
24 | | -To bring us onto the same page - and this should not be controversial - I’ll share my attitude towards DevOps, where I see it being valuable and beneficial when building products and services. |
25 | | - |
26 | | -Pitfalls: When Reality meets Ideology |
27 | | -Drawing on my personal experience I will share a number of examples, where despite best intentions, our DevOps endeavours, descended into, at best waste and pain, at worst total dysfunction. I will touch on aspects such as technology ‘greed’, over-engineering, gold-plating, premature optimisation, strategic misalignment and others, and show how, from excitement and enthusiasm about DevOps users, stakeholders and ‘the business’ can easily become disillusioned, cynical and frustrated. |
28 | | - |
29 | | -Conclusion: The moral of the tale, advice for the real world |
30 | | -I will conclude with guiding principles to avoid falling into the same traps. |
31 | | - |
32 | | -What participants will take away: |
33 | | -An awareness of the important to adopt a critical view on |
34 | | -- DevOps (and other) technical decisions |
35 | | -- A list of potential pitfalls and challenges |
36 | | -- Actionable guidance and suggestions on how to manage these tensions, risks and challenges to avoid falling into the same traps |
| 1 | ++++ |
| 2 | +City = "Zurich" |
| 3 | +Year = "2025" |
| 4 | +talk_date = "2025-03-13" |
| 5 | +talk_start_time = "14:25" |
| 6 | +talk_end_time = "14:30" |
| 7 | +title = "How I Started Worrying and Stopped Loving DevOps" |
| 8 | +type = "talk" |
| 9 | +speakers = ["marcel-britsch"] |
| 10 | +youtube = "YMK4lgZjV54" |
| 11 | +vimeo = "1070639076" |
| 12 | +speakerdeck = "" |
| 13 | +slideshare = "" |
| 14 | +slides = "" |
| 15 | ++++ |
| 16 | + |
| 17 | +### Ignite |
| 18 | + |
| 19 | +Summary: |
| 20 | +In this cautionary tale, I’ll share three real-world product-building experiences, mapping my journey as a product manager from a DevOps enthusiast to a wary cynic. I’ll share examples of how infrastructure can drift into ‘purgatory’: pipelines that are ‘never done,’ painfully complex to maintain, or beautifully engineered yet devoid of applications to support. My goal is to highlight the missteps I encountered, so future teams might avoid these traps and sidestep the costly pursuit of infrastructure perfection that can derail real progress. |
| 21 | + |
| 22 | +How the talk will unfold: |
| 23 | +Introduction: The Allure of DevOps |
| 24 | +To bring us onto the same page - and this should not be controversial - I’ll share my attitude towards DevOps, where I see it being valuable and beneficial when building products and services. |
| 25 | + |
| 26 | +Pitfalls: When Reality meets Ideology |
| 27 | +Drawing on my personal experience I will share a number of examples, where despite best intentions, our DevOps endeavours, descended into, at best waste and pain, at worst total dysfunction. I will touch on aspects such as technology ‘greed’, over-engineering, gold-plating, premature optimisation, strategic misalignment and others, and show how, from excitement and enthusiasm about DevOps users, stakeholders and ‘the business’ can easily become disillusioned, cynical and frustrated. |
| 28 | + |
| 29 | +Conclusion: The moral of the tale, advice for the real world |
| 30 | +I will conclude with guiding principles to avoid falling into the same traps. |
| 31 | + |
| 32 | +What participants will take away: |
| 33 | +An awareness of the important to adopt a critical view on |
| 34 | +- DevOps (and other) technical decisions |
| 35 | +- A list of potential pitfalls and challenges |
| 36 | +- Actionable guidance and suggestions on how to manage these tensions, risks and challenges to avoid falling into the same traps |
37 | 37 | - An understanding that infrastructure is an important - but nevertheless - means to an end, that needs to serve a greater purpose |
0 commit comments