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
170
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
360
Bastardised Kanban
chids
0
1.5k
Heroku as a production platform
chids
0
180
Opinions on DevOps
chids
2
630
REST - Valtech
chids
4
390
The OPS side of DEV
chids
9
4.6k
[Swedish] NoSQL at Javaforum Stockholm
chids
2
170
Approaching and evaluating NoSQL
chids
3
180
Automation @ Hitta.se and why it happened
chids
1
270
Other Decks in Technology
See All in Technology
「AI駆動PO」を考えてみる - 作る速さから価値のスループットへ:検査・適応で未来を開発 / AI-driven product owner. scrummat2025
yosuke_nagai
4
580
成長自己責任時代のあるきかた/How to navigate the era of personal responsibility for growth
kwappa
3
270
多野優介
tanoyusuke
1
420
「技術負債にならない・間違えない」 権限管理の設計と実装
naro143
36
11k
PLaMo2シリーズのvLLM実装 / PFN LLM セミナー
pfn
PRO
2
970
SwiftUIのGeometryReaderとScrollViewを基礎から応用まで学び直す:設計と活用事例
fumiyasac0921
0
140
stupid jj tricks
indirect
0
7.9k
生成AI_その前_に_マルチクラウド時代の信頼できるデータを支えるSnowflakeメタデータ活用術.pdf
cm_mikami
0
110
バイブコーディングと継続的デプロイメント
nwiizo
2
410
GopherCon Tour 概略
logica0419
2
190
20201008_ファインディ_品質意識を育てる役目は人かAIか___2_.pdf
findy_eventslides
0
120
コンテキストエンジニアリングとは? 考え方と応用方法
findy_eventslides
4
890
Featured
See All Featured
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.1k
Measuring & Analyzing Core Web Vitals
bluesmoon
9
610
Unsuck your backbone
ammeep
671
58k
Building an army of robots
kneath
306
46k
Thoughts on Productivity
jonyablonski
70
4.9k
GraphQLとの向き合い方2022年版
quramy
49
14k
Bash Introduction
62gerente
615
210k
Into the Great Unknown - MozCon
thekraken
40
2.1k
Mobile First: as difficult as doing things right
swwweet
224
10k
Code Reviewing Like a Champion
maltzj
525
40k
Practical Orchestrator
shlominoach
190
11k
Visualization
eitanlees
148
16k
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”