Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
DevOps @ KnowIT
Search
Mårten Gustafson
November 12, 2013
Technology
0
140
DevOps @ KnowIT
Talk on DevOps at a breakfast seminar hosted by KnowIT.
Mårten Gustafson
November 12, 2013
Tweet
Share
More Decks by Mårten Gustafson
See All by Mårten Gustafson
Github all the things!
chids
3
330
Bastardised Kanban
chids
0
1.4k
Heroku as a production platform
chids
0
150
Opinions on DevOps
chids
2
590
REST - Valtech
chids
4
360
The OPS side of DEV
chids
9
4.5k
[Swedish] NoSQL at Javaforum Stockholm
chids
2
130
Approaching and evaluating NoSQL
chids
3
150
Automation @ Hitta.se and why it happened
chids
1
240
Other Decks in Technology
See All in Technology
Taming you application's environments
salaboy
0
200
OCI Security サービス 概要
oracle4engineer
PRO
0
6.5k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
0
110
マルチプロダクトな開発組織で 「開発生産性」に向き合うために試みたこと / Improving Multi-Product Dev Productivity
sugamasao
1
310
rootlessコンテナのすゝめ - 研究室サーバーでもできる安全なコンテナ管理
kitsuya0828
3
390
心が動くエンジニアリング ── 私が夢中になる理由
16bitidol
0
100
AIチャットボット開発への生成AI活用
ryomrt
0
170
Introduction to Works of ML Engineer in LY Corporation
lycorp_recruit_jp
0
140
アジャイルチームがらしさを発揮するための目標づくり / Making the goal and enabling the team
kakehashi
3
150
20241120_JAWS_東京_ランチタイムLT#17_AWS認定全冠の先へ
tsumita
2
300
AGIについてChatGPTに聞いてみた
blueb
0
130
Incident Response Practices: Waroom's Features and Future Challenges
rrreeeyyy
0
160
Featured
See All Featured
Raft: Consensus for Rubyists
vanstee
136
6.6k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
232
17k
No one is an island. Learnings from fostering a developers community.
thoeni
19
3k
Code Review Best Practice
trishagee
64
17k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
6
430
Put a Button on it: Removing Barriers to Going Fast.
kastner
59
3.5k
Java REST API Framework Comparison - PWX 2021
mraible
PRO
28
8.2k
10 Git Anti Patterns You Should be Aware of
lemiorhan
655
59k
It's Worth the Effort
3n
183
27k
A designer walks into a library…
pauljervisheath
204
24k
Agile that works and the tools we love
rasmusluckow
327
21k
Practical Orchestrator
shlominoach
186
10k
Transcript
Hello!
* I’m Mårten * I tend to work at companies
with blue logos
* Today, this: Omni * 13 devs (backend: 7+3 &
frontend: 2+2) * I head up the backend & infrastructure team
Infrastructure aware development and vice versa
Why?
Awareness * Become aware of what happens outside “our bubble”
* Become aware of why “things” are happening
Understanding * Understanding why things are the eay they are
* Understanding that what appears bad to me, might appear good to someone else
Precision * Less confustion * Higher pace * Quicker to
find the “right direction”
Co-planning * If we understand and are aware it’ll be
easier to plan together * If we plan together we’ll become aware and understand each other
We’re on the same team!
“No, we’re not!” * (get a grip)
co-lo get a sysops * in your team * (per
team?) * contract or hire * full or part-time
managed hosting customer responsible technician * whom you assimilate! *
get person on chat, mailing lists, etc * invite to lunch, AW, whatever
cloud == co-lo get a sysops * I consider cloud
based servers as co-lo
PaaS sysop 2.0? * PaaS, e.g. Heroku, will force a
bigger responsibility on DEV * and/or a completely different kind of OPS * I’m not sure here, yet
How?
Don’t know. * There’s no exact answer as to “how”
Why?
Higher pace. * Do X in half the time? *
Do X with half the people involved? * More time and or people to do Y and Z!
Higher quality. * Avoid the most common mishaps? (without loosing
pace!)
Higher awareness.
Higher engagement. * if more of the involved have higher
awareness we’ll get a higher engagement and we’ll increase quality and deliver faster
Key. Words.
Cooperate. * Make it natural * Make it easy
Communicate. * Direct, clear, concise, transparent
The rest will “sort itself” out. * Not quite, but
almost
Hints
Find “like-minded”
Invite. * Invite all “the others” to planning, stand-ups, coffee,
AW, etc * As with all transformations it won’t happen in an instant and it’ll be shaped over time
Guerrilla cooperation. * (my personal favorite) * Tend to work
really well * Easier to ask for forgiveness than approval
None
1. Get to know each other
1. Get to know each other 2. Involve each other
1. Get to know each other 2. Involve each other
3. Start doing things together
1. Get to know each other 2. Involve each other
3. Start doing things together 4. Think strategic together
1. Get to know each other 2. Involve each other
3. Start doing things together 4. Think strategic together 5. Stop viewing others as “others”
1. Get to know each other 2. Involve each other
3. Start doing things together 4. Think strategic together 5. Stop viewing others as “others” 6. Do a project together
Culture. * DevOps is culture * DevOps is not an
automated infrastructure (automation is a product, project, whatevs) * DevOps is not a title * Culture happens when individuals work together
“An organizations culture isn’t in ‘the walls’. It’s in the
people”