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.3k
Heroku as a production platform
chids
0
140
Opinions on DevOps
chids
2
580
REST - Valtech
chids
4
350
The OPS side of DEV
chids
9
4.5k
[Swedish] NoSQL at Javaforum Stockholm
chids
2
120
Approaching and evaluating NoSQL
chids
3
150
Automation @ Hitta.se and why it happened
chids
1
230
Other Decks in Technology
See All in Technology
Azureの基本的な権限管理の勉強会
yhana
1
2.2k
CockroachDB はどのくらい「しぶとい」のか? / How tough is CockroachDB?
kota2and3kan
6
4k
AWS学習者向けにAzureの解説スライドを作成した話
handy
3
220
require(ESM)とECMAScript仕様
uhyo
4
1k
Oracle Base Database Service 技術詳細
oracle4engineer
PRO
5
37k
Building Dashboards as a Hobby
egmc
0
430
今さら聞けないDocker入門 〜 Dockerfileのベストプラクティス編
devops_vtj
22
6.7k
生成AIと産業向けソフトウェアの自動生成 〜 ハノーバーメッセ2024より〜
kioto
2
280
MixIT 2024 - Pulumi : Gérer son infra avec son langage de programmation préféré
ju_hnny5
1
130
uvを使ってストレスフリーな Python開発をしよう!
r74tech
0
260
Grafana x PagerDuty Better Together
jacopen
1
340
類似ロジック実装をiOS/Android間で合わせる道標No.1
fumiyasac0921
1
180
Featured
See All Featured
Building Effective Engineering Teams - LeadDev
addyosmani
32
1.9k
Debugging Ruby Performance
tmm1
70
11k
What's in a price? How to price your products and services
michaelherold
238
11k
Design by the Numbers
sachag
274
18k
Git: the NoSQL Database
bkeepers
PRO
423
63k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
660
120k
What's new in Ruby 2.0
geeforr
337
31k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
14
8.4k
WebSockets: Embracing the real-time Web
robhawkes
59
7k
Pencils Down: Stop Designing & Start Developing
hursman
117
11k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
275
13k
Happy Clients
brianwarren
92
6.4k
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”