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
350
Bastardised Kanban
chids
0
1.5k
Heroku as a production platform
chids
0
170
Opinions on DevOps
chids
2
620
REST - Valtech
chids
4
390
The OPS side of DEV
chids
9
4.6k
[Swedish] NoSQL at Javaforum Stockholm
chids
2
160
Approaching and evaluating NoSQL
chids
3
170
Automation @ Hitta.se and why it happened
chids
1
270
Other Decks in Technology
See All in Technology
Delta airlines®️ USA Contact Numbers: Complete 2025 Support Guide
airtravelguide
0
340
敢えて生成AIを使わないマネジメント業務
kzkmaeda
2
440
生まれ変わった AWS Security Hub (Preview) を紹介 #reInforce_osaka / reInforce New Security Hub
masahirokawahara
0
470
OSSのSNSツール「Misskey」をさわってみよう(右下ワイプで私のOSCの20年を振り返ります) / 20250705-osc2025-do
akkiesoft
0
160
AI専用のリンターを作る #yumemi_patch
bengo4com
5
4.3k
事業成長の裏側:エンジニア組織と開発生産性の進化 / 20250703 Rinto Ikenoue
shift_evolve
PRO
2
21k
20250705 Headlamp: 專注可擴展性的 Kubernetes 用戶界面
pichuang
0
270
開発生産性を組織全体の「生産性」へ! 部門間連携の壁を越える実践的ステップ
sudo5in5k
2
7k
IPA&AWSダブル全冠が明かす、人生を変えた勉強法のすべて
iwamot
PRO
2
120
Operating Operator
shhnjk
1
580
KubeCon + CloudNativeCon Japan 2025 Recap
ren510dev
1
380
開発生産性を測る前にやるべきこと - 組織改善の実践 / Before Measuring Dev Productivity
kaonavi
9
4.2k
Featured
See All Featured
Large-scale JavaScript Application Architecture
addyosmani
512
110k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
8
820
A Modern Web Designer's Workflow
chriscoyier
695
190k
Building Better People: How to give real-time feedback that sticks.
wjessup
367
19k
Measuring & Analyzing Core Web Vitals
bluesmoon
7
510
Balancing Empowerment & Direction
lara
1
430
Producing Creativity
orderedlist
PRO
346
40k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
2.4k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
740
Art, The Web, and Tiny UX
lynnandtonic
299
21k
RailsConf 2023
tenderlove
30
1.1k
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”