You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/posts/171101-continuous-delivery-devops-you.markdown
+66-13Lines changed: 66 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,8 +12,9 @@ This blog post contains the slides along with a loose transcript and
12
12
additional resources from my technical talk on DevOps and Continuous
13
13
Delivery concepts given at my alma mater, the University of Virginia,
14
14
to the [M.S. in Management of Information Technology program](https://www.commerce.virginia.edu/ms-mit) on November 2nd and 4th of 2017.
15
+
15
16
Links to learn more about the concepts presented in this talk can
16
-
be found at the bottom of the page.
17
+
be found in the sidebar and at the bottom of this page.
17
18
18
19
----
19
20
@@ -30,52 +31,104 @@ where over 125,000 developers read each month to learn how to
30
31
31
32
<imgsrc="/img/171101-devops-cd-you/devops-cd-you.004.jpg"width="100%"class="technical-diagram img-rounded"style="border: 1pxsolid#aaa"alt="What's the point of Agile?">
32
33
33
-
...
34
+
You've talked about using the Agile software development methodology
35
+
on your teams, but what's the purpose? Why does Agile development matter
As well as in the Kubernetes logo in the form of a ship steering wheel.
49
63
50
64
51
65
<imgsrc="/img/171101-devops-cd-you/devops-cd-you.008.jpg"width="100%"class="technical-diagram img-rounded"style="border: 1pxsolid#aaa"alt="Agile sprints need to ship code into production to create anything of value.">
52
66
53
-
...
67
+
Here is a super high-level diagram of the ideal scenario we need for
68
+
Agile development teams. Create working code and get it shipped as soon
69
+
as possible into production.
54
70
55
71
56
72
<imgsrc="/img/171101-devops-cd-you/devops-cd-you.009.jpg"width="100%"class="technical-diagram img-rounded"style="border: 1pxsolid#aaa"alt="Move fast and break things.">
57
73
58
-
...
74
+
Facebook's internal motto used to be "Move fast and break things." They
75
+
thought that if you aren't breaking things then you aren't moving fast
76
+
enough.
59
77
60
78
61
79
<imgsrc="/img/171101-devops-cd-you/devops-cd-you.010.jpg"width="100%"class="technical-diagram img-rounded"style="border: 1pxsolid#aaa"alt="If you do not have the right processes and tools in place eventually production will break.">
62
80
63
-
...
81
+
And eventually if you're constantly shipping to production and you do not
82
+
have the appropriate processes and tools in place, your applications
83
+
will break. The breakage has nothing to do with the Agile methodology
84
+
itself.
85
+
86
+
Your team and organization will come to a fork in the road when you
87
+
end up with a broken environment.
64
88
65
89
66
90
<imgsrc="/img/171101-devops-cd-you/devops-cd-you.011.jpg"width="100%"class="technical-diagram img-rounded"style="border: 1pxsolid#aaa"alt="Fight the urge to put manual processes in place that slow you down. You must automate.">
67
91
68
-
...
92
+
Traditionally, organizations have tried to prevent breakage by putting
93
+
more manual tools and processes in place. Manual labor slows... down...
94
+
your... ability... to... execute.
95
+
96
+
This is one path provided by the fork in the road. Put your "Enterprise
97
+
Change Review Boards" in place. Require production sign-offs by some
98
+
Executive Vice President who has never written a line of code in his life.
99
+
Put several dozen "technical architects" in a room together to argue over
100
+
who gets to deploy their changes to production that month.
101
+
102
+
The manual path is insanity. Eventually the best developers in your
103
+
organization will get frustrated and leave. Executives will ask why
104
+
nothing ever gets done. Why does it take our organization three years
105
+
to ship a small change to a critical application?
69
106
70
107
71
108
<imgsrc="/img/171101-devops-cd-you/devops-cd-you.012.jpg"width="100%"class="technical-diagram img-rounded"style="border: 1pxsolid#aaa"alt="Some teams try to get around the production problem by shipping to dev, but they still are not creating value.">
72
109
73
-
...
110
+
Some development teams try to get around the manual production challenges
111
+
by shipping everything to a development environment. The dev environment is
112
+
under their control.
113
+
114
+
But what's the huge glaring problem in this situation?
115
+
116
+
If you are not shipping to production, then you are not creating any value
117
+
for your users. The teams have made a rational decision to ship to development
118
+
but the organization still suffers due to the manual controls.
74
119
75
120
76
121
<imgsrc="/img/171101-devops-cd-you/devops-cd-you.013.jpg"width="100%"class="technical-diagram img-rounded"style="border: 1pxsolid#aaa"alt="This session is about DevOps and Continuous Delivery.">
77
122
78
-
...
123
+
The problems we are talking about are created by the Agile methodology
124
+
because they become acute when your development team is producing code at
125
+
high velocity. Once code is created faster, you need a way to reliably,
126
+
consistently put the code into production so that it can create value for
127
+
its users.
128
+
129
+
DevOps and Continuous Delivery are the broad terms that encompass how to
130
+
reliably ship code to production and operate it when the code is running in
131
+
production.
79
132
80
133
81
134
<imgsrc="/img/171101-devops-cd-you/devops-cd-you.014.jpg"width="100%"class="technical-diagram img-rounded"style="border: 1pxsolid#aaa"alt="What DevOps is NOT.">
0 commit comments