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
Stitching it Together
Search
Charlie Robbins
October 06, 2012
Programming
0
89
Stitching it Together
My talk from Cloud Tech III:
http://www.meetup.com/cloudcomputing/events/56678082/
Charlie Robbins
October 06, 2012
Tweet
Share
More Decks by Charlie Robbins
See All by Charlie Robbins
Flexible Design Systems
indexzero
0
53
Exploring Leadership, Mangement, and Mentorship In Open Source
indexzero
0
6
Delivering Flexible Cross Platform Design Systems
indexzero
0
620
Scaling Webpack to Thousands of Concurrent Builds
indexzero
1
180
Everything You Wanted to Know About Logging
indexzero
1
170
Exploring Leadership, Mangement, and Mentorship in Open Source
indexzero
1
110
Serverless Front-End Deployments using npm
indexzero
2
190
Understanding the npm wire API
indexzero
0
310
Node.js @ GoDaddy in 2015
indexzero
1
110
Other Decks in Programming
See All in Programming
『自分のデータだけ見せたい!』を叶える──Laravel × Casbin で複雑権限をスッキリ解きほぐす 25 分
akitotsukahara
2
630
A full stack side project webapp all in Kotlin (KotlinConf 2025)
dankim
0
110
コードの90%をAIが書く世界で何が待っているのか / What awaits us in a world where 90% of the code is written by AI
rkaga
51
33k
AIともっと楽するE2Eテスト
myohei
0
310
レベル1の開発生産性向上に取り組む − 日々の作業の効率化・自動化を通じた改善活動
kesoji
0
120
ISUCON研修おかわり会 講義スライド
arfes0e2b3c
1
430
地方に住むエンジニアの残酷な現実とキャリア論
ichimichi
5
1.5k
Claude Code + Container Use と Cursor で作る ローカル並列開発環境のススメ / ccc local dev
kaelaela
5
2.2k
PostgreSQLのRow Level SecurityをPHPのORMで扱う Eloquent vs Doctrine #phpcon #track2
77web
2
510
チームのテスト力を総合的に鍛えて品質、スピード、レジリエンスを共立させる/Testing approach that improves quality, speed, and resilience
goyoki
4
720
Modern Angular with Signals and Signal Store:New Rules for Your Architecture @enterJS Advanced Angular Day 2025
manfredsteyer
PRO
0
210
「テストは愚直&&網羅的に書くほどよい」という誤解 / Test Smarter, Not Harder
munetoshi
0
150
Featured
See All Featured
KATA
mclloyd
30
14k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
20
1.3k
The Illustrated Children's Guide to Kubernetes
chrisshort
48
50k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.5k
Navigating Team Friction
lara
187
15k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
26k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
657
60k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
357
30k
Docker and Python
trallard
44
3.5k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
35
2.4k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
507
140k
Measuring & Analyzing Core Web Vitals
bluesmoon
7
500
Transcript
Stitching it Together
None
These are just my observations and should not be construed
as the "one true way to do anything."
I am a "boss"
But I am also an engineer
None
From what I've observed it's all starts with servers.
Well .... servers and source code.
Oh .... and people. Lots and lots of people.
So what are you building?
You need to provision some servers somewhere.
Like maybe a cloud. That's sounds good right?
Provisioning
fog || libcloud || whatever
You need it to be highly repeatable over various networks
Orchestration
And they should probably be consistent.
Configuration Management
puppet || chef || custom || whatever
Package Management
None
Once servers are running, they should stay running.
You want your servers on your radar.
Monitoring
newrelic || nagios || whatever
"Dashboards"
You want to put new files onto your servers
Deployment
None
Servers will most certainly always have problems.
And someone should probably do something about that.
Alerting
pagerduty || twilio || whatever
So ... who is building it?
It's really all about the people building your infrastructure.
People like to think and have ideas.
People have dreams and aspirations.
People have fears and stresses.
People want to be happy.
People make the most important choices outside of their work.
People hate being ignored or feeling invisible.
People need to communicate.
But people have problems communicating .
It is really all about fostering communication and conversation around
what you're doing. And why you're doing it.
So getting to the point ...
... with all these vendors....
... and all of these people ...
... why is this still so much work?!
It's like you need to be a detective just to
get by.
Or maybe just a tuning fork for the cloud.
"What did the documentation say?"
"Whose cellphone is setup to receive those alerts?"
"Why did everything break and fallover?"
After a while you are left completely drained
I've observed that it's really two fundamental problems.
We are generally stitching together solutions that are not designed
to work together holistically.
We cannot (or will not) go the last mile for
incident response and resolution.
Because people really only pay attention when things are broken!
OH! And way too many EMAILS
Why is no one trying to fix this problem?
― KRS-One “If you don't repeat the patterns of your
own success you won't be successful. You've gotta know your own formula; what made you ... "you".”
None
None
None
Incompleteness Theorem
None
― Tyler Durden “The ability to let the things which
do not matter truly slide”
“ Special thanks to the Noun Project ― thenounproject.com ”
End