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
How devops improved my dev
Search
Florian Gilcher
April 18, 2013
Programming
5
1.5k
How devops improved my dev
Florian Gilcher
April 18, 2013
Tweet
Share
More Decks by Florian Gilcher
See All by Florian Gilcher
A new contract with users
skade
1
480
Using Rust to interface with my dive computer
skade
0
230
async/.await with async-std
skade
1
780
Training Rust
skade
1
99
Internet of Streams - IoT in Rust
skade
0
84
How DevRel is failing communities
skade
0
72
The power of the where clause
skade
0
620
Three Years of Rust
skade
1
170
Rust as a CLI language
skade
1
200
Other Decks in Programming
See All in Programming
生成AIコーディングとの向き合い方、AIと共創するという考え方 / How to deal with generative AI coding and the concept of co-creating with AI
seike460
PRO
1
360
Webの外へ飛び出せ NativePHPが切り拓くPHPの未来
takuyakatsusa
2
530
スタートアップの急成長を支えるプラットフォームエンジニアリングと組織戦略
sutochin26
0
4.2k
なぜ「共通化」を考え、失敗を繰り返すのか
rinchoku
1
640
NPOでのDevinの活用
codeforeveryone
0
790
「Cursor/Devin全社導入の理想と現実」のその後
saitoryc
0
770
PHPで始める振る舞い駆動開発(Behaviour-Driven Development)
ohmori_yusuke
2
330
AIエージェントはこう育てる - GitHub Copilot Agentとチームの共進化サイクル
koboriakira
0
510
dbt民主化とLLMによる開発ブースト ~ AI Readyな分析サイクルを目指して ~
yoshyum
3
800
PipeCDのプラグイン化で目指すところ
warashi
1
260
たった 1 枚の PHP ファイルで実装する MCP サーバ / MCP Server with Vanilla PHP
okashoi
1
230
チームで開発し事業を加速するための"良い"設計の考え方 @ サポーターズCoLab 2025-07-08
agatan
0
210
Featured
See All Featured
The Invisible Side of Design
smashingmag
301
51k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
181
53k
Documentation Writing (for coders)
carmenintech
72
4.9k
Code Review Best Practice
trishagee
69
18k
KATA
mclloyd
30
14k
Adopting Sorbet at Scale
ufuk
77
9.4k
Into the Great Unknown - MozCon
thekraken
39
1.9k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Building a Modern Day E-commerce SEO Strategy
aleyda
42
7.4k
Making the Leap to Tech Lead
cromwellryan
134
9.4k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
30
2.1k
Transcript
None
None
The hotel wireless was terrible, sorry for the lack of
pictures.
$ whoami
$ whoami $ cat .profile | grep export export GIT_AUTHOR="Florian
Gilcher" export GIT_AUTHOR_EMAIL="
[email protected]
" export GITHUB_NICK="skade" export GITHUB_ORGANIZATIONS="asquera,padrino" export TWITTER_NICK="@argorak" export TM_COMPANY="Asquera GmbH"
@argorak
$ whoami Ruby Programmer since 2003 Now a consultant specialising
in backends... ... and team building. I run usergroups and organize conferences as a hobby.
http://asquera.de
http://padrinorb.com
http://eurucamp.org
“I don’t want to be woken up at night, so
I call myself a developer.”
I set out to present a more dev-minded perspective on
devops.
That was harder then I thought...
There’s a talk about the “transforming devs to devops” later
on.
git push developer mindsets/devops
Whats the benefit, if you don’t do a lot of
ops?
Vagrant Puppet Chef
Vagrant Puppet Chef
How did a devops mindset improve the software I write?
A bit of history about myself
I started my career in a typical agency job.
LAMP and the DEV/OPS split.
It wasn’t even that bad...
...until projects got special.
scale scope
Suddenly it turned out that one of the most efficient
teams was an admin, a programmer and a cup of coffee.
Example
An example One of our clients imports and reencodes videos
from a constantly changing number of sources each day.
Sources FTP upload FTP fetch RSS feeds RSS feeds that
are no RSS feeds And some more...
Destinations All of them need to be reencoded to a
standard set of sizes and bitrates.
Simple approach
Single program with architecture
Same architecture, 3 processes
Why?
Videos per day
Critical failures last year
Deployments last year
New ways of discussing things.
None
None
Practical things learned in the process.
... beyond writing daemons and stuff.
A different perspective on code.
Infrastructure as code.
Code for infrastructure.
Common CLI tools Common configurations styles Common way of doing
things
Gives insight Well managable Well automatable
In general, I care less about internal quality of programs
nowadays then about external quality.
My ugliest piece of code ran 1,5 years in production
without a change.
Nobody ever noticed how horrible it was.
I evaluate new software differently.
“Ease of setup” is a red flag.
This especially applies to new and fancy databases.
Not having to push any buttons to start working a
database is problematic, if not dangerous.
You might miss things along the way.
“Ease of non-trivial configuration” is far more important.
How to grade that?
Set up a production-like system.
Keep tally marks on how often it leaves you puzzled.
There is no such thing as “setting up production too
early.”
Everything before that is childs play.
The big bangs always happen in production.
My favourite: Expensive loadbalancers that die during configuration and need
to be shipped to the manufacturer.
Teams need to get used to their own systems.
Metrics and Logging are important in complex systems.
Most pure development teams underrate them and implement them too
late.
They should be there from day one.
Last but not least: internal tooling can save you a
lot of work.
Creative ways to talk about it even more.
None
But what about the humans?
Giving people say in many things makes them discuss many
things.
There are two things I rarely see in teams with
strict roles.
1. Platform refactorings
Why? It always means that individual roles loose ground.
Why? This can get political very quick.
Why? Lack of skill.
2. Code reviews
Why? Not enough staff that “is qualified” to review certain
code.
The devops mindset takes away a lot of friction.
Less asking permission, more doing.
When your frontend developer changes your backend API, your varnish
config, your deployment scripts and the puppet manifests before handing stuff off to review to implement a new feature, you are there.
Bonus points if said developer is the companies apprentice.
The devops mindset can be incredibly empowering.
Devops-minded teams can cope with missing team members easier.
Everyone knows what everything is roughly doing anyways.
Find hacks to gather and spread that knowledge across your
team!
None
To sum up:
Teams with a strong devops culture: can handle more complexity
Teams with a strong devops culture: can handle more complexity
can find more alternative approaches to problems.
Teams with a strong devops culture: can handle more complexity
can find more alternative approaches to problems. are more likely to find solutions that handle well in production.
Their immediate answers are more complex.
Thank you for listening.
How did devops change your development style?