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
CDK Vibe Coding Fes
tomoki10
1
630
An introduction to Claude Code SDK
choplin
2
1k
AI時代にも変わらぬ価値を発揮したい: インフラ・クラウドを切り口にユーザー価値と非機能要件に向き合ってエンジニアとしての地力を培う
netmarkjp
0
130
ポストコロナ時代の SaaS におけるコスト削減の意義
izzii
1
470
SREの次のキャリアの道しるべ 〜SREがマネジメントレイヤーに挑戦して、 気づいたこととTips〜
coconala_engineer
1
4.3k
microCMSではじめるAIライティング
himaratsu
0
150
データ戦略部門 紹介資料
sansan33
PRO
1
3.3k
Amazon SNSサブスクリプションの誤解除を防ぐ
y_sakata
3
190
ゼロから始めるSREの事業貢献 - 生成AI時代のSRE成長戦略と実践 / Starting SRE from Day One
shinyorke
PRO
0
110
Figma Dev Mode MCP Serverを用いたUI開発
zoothezoo
0
230
VS CodeとGitHub Copilotで爆速開発!アップデートの波に乗るおさらい会 / Rapid Development with VS Code and GitHub Copilot: Catch the Latest Wave
yamachu
3
460
Talk to Someone At Delta Airlines™️ USA Contact Numbers
travelcarecenter
0
160
Featured
See All Featured
How STYLIGHT went responsive
nonsquared
100
5.6k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.5k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
282
13k
Code Reviewing Like a Champion
maltzj
524
40k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
Unsuck your backbone
ammeep
671
58k
YesSQL, Process and Tooling at Scale
rocio
173
14k
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
126
53k
The World Runs on Bad Software
bkeepers
PRO
70
11k
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
229
22k
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”