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
ソフトウェア品質を数字で捉える技術。事業成長を支えるシステム品質の マネジメント
takuya542
1
7k
Code as Context 〜 1にコードで 2にリンタ 34がなくて 5にルール? 〜
yodakeisuke
0
120
AIコーディング道場勉強会#2 君(エンジニア)たちはどう生きるか
misakiotb
1
280
AIエージェントはこう育てる - GitHub Copilot Agentとチームの共進化サイクル
koboriakira
0
490
Modern Angular with Signals and Signal Store:New Rules for Your Architecture @enterJS Advanced Angular Day 2025
manfredsteyer
PRO
0
180
Webの外へ飛び出せ NativePHPが切り拓くPHPの未来
takuyakatsusa
2
490
第9回 情シス転職ミートアップ 株式会社IVRy(アイブリー)の紹介
ivry_presentationmaterials
1
260
Team operations that are not burdened by SRE
kazatohiei
1
300
エンジニア向け採用ピッチ資料
inusan
0
180
AWS CDKの推しポイント 〜CloudFormationと比較してみた〜
akihisaikeda
3
320
生成AIコーディングとの向き合い方、AIと共創するという考え方 / How to deal with generative AI coding and the concept of co-creating with AI
seike460
PRO
1
350
PHP 8.4の新機能「プロパティフック」から学ぶオブジェクト指向設計とリスコフの置換原則
kentaroutakeda
2
730
Featured
See All Featured
Gamification - CAS2011
davidbonilla
81
5.3k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
48
5.4k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
730
Measuring & Analyzing Core Web Vitals
bluesmoon
7
500
How to Think Like a Performance Engineer
csswizardry
24
1.7k
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
Designing for humans not robots
tammielis
253
25k
Raft: Consensus for Rubyists
vanstee
140
7k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
35
2.4k
Bootstrapping a Software Product
garrettdimon
PRO
307
110k
Designing Experiences People Love
moore
142
24k
What's in a price? How to price your products and services
michaelherold
246
12k
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