Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Recap of Jordan DeaMattson TechTalk
Search
Kuncara Adi Nugraha
April 29, 2015
Technology
380
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Recap of Jordan DeaMattson TechTalk
Small recap from Jordan DeaMattson tech talk in Onebitmedia, Yogyakarta
Kuncara Adi Nugraha
April 29, 2015
More Decks by Kuncara Adi Nugraha
See All by Kuncara Adi Nugraha
Recap of Dicoding Events : Continuous Quality and Test Automations
lagilaper
0
310
Legacy codes
lagilaper
0
3.2k
Metrics and Monitoring
lagilaper
0
91
Agile Retrospective
lagilaper
0
210
Culture Test
lagilaper
0
210
Introduction to Vagrant and Docker
lagilaper
0
110
Other Decks in Technology
See All in Technology
カンファレンスに参加した後の浮遊感とセルフケア
pauli
0
270
HolmesGPTで始めるSREエージェント入門!プラットフォームの障害調査はAIにお任せ 〜
sanghyuk
0
250
GitHub Agentic Workflows を触ってみる
htkym
2
910
Databricksメトリクスビューはじめてのもくもく会
taka_aki
0
150
AI臭い文章とは何なのか
nasuvitz
37
76k
いちAWSエンジニアのAI活用を振り返る #devio2026 / devio osaka 2026 kawahara
masahirokawahara
1
300
【Findyテック文化祭ワークショップ】新卒エンジニア&採用担当と作る、 なりたい姿と今やるべき一歩
dip_tech
PRO
0
150
20260929_AmazonGuardDutyの検出通知メールにAWS DevOpsAgentの調査結果を追加する
yhana
1
400
AWS FinOps Agent 結局何が得意なの?
siromi
0
230
スキルを作る、その前に!複数人で使われるスキルを 作るためのプロセス
junkifurukawa
1
150
IR Today: Theory, Practice, and Agents
dtunkelang
0
310
セルフサービスのオブザーバビリティ基盤をOpenTelemetryで作る / Building a Self-Service Observability Platform with OpenTelemetry
ymotongpoo
3
500
Featured
See All Featured
Discover your Explorer Soul
emna__ayadi
2
1.3k
GraphQLの誤解/rethinking-graphql
sonatard
75
12k
Pawsitive SEO: Lessons from My Dog (and Many Mistakes) on Thriving as a Consultant in the Age of AI
davidcarrasco
0
250
From Legacy to Launchpad: Building Startup-Ready Communities
dugsong
0
340
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
35
2.9k
Code Review Best Practice
trishagee
74
20k
Site-Speed That Sticks
csswizardry
13
1.5k
RailsConf 2023
tenderlove
30
1.6k
A designer walks into a library…
pauljervisheath
211
25k
SEOcharity - Dark patterns in SEO and UX: How to avoid them and build a more ethical web
sarafernandez
0
290
YesSQL, Process and Tooling at Scale
rocio
174
15k
Claude Code のすすめ
schroneko
67
230k
Transcript
Recap of Meet & Greet with Jordan DM
Topics 1. Five Whys 2. Metrics and Analytics 3. Pick
a Boring Tech 4. Devops as a culture
Five Whys Simplest tool for root-cause analysis Useful for management
roles Useful for postmortem / post-hoc explanations Pitfall: 1. Sometimes “how” is better 2. It might lead to blaming people
Metrics / Data Driven Principles: 1. Assign owners 2. Create
layered metrics, e.g: • Business metrics • Development metrics • Infrastructure metrics 3. Analyze and use for taking decision
Metrics / Data Driven(2) credits: Dan McKinley
Metrics / Data Driven(3) credits: Dan McKinley
Pick a boring techs Innovations tokens concepts Boring ≠ Bad
Boring means well-understood and lesser unknown situations / variables Credit: Dan McKinley
Pick a boring techs (2) Redefine “best tool for the
job” • Our job is “keep our company in business and make us still eat tomorrow” • Best tool is “keep problems as minimum as possible and solve requirement as maximum as possible” Credit: Dan McKinley
Pick a boring techs (3) How to pick new techs?
1. Let’s talk first 2. Can we solve with our current techs? 3. Addition or alternatives? Set clear expectations for migration Credit: Dan McKinley
DevOps as Culture DevOps is not only tools Culture movement
combined with development practices to enable rapid development
DevOps as Culture(2) 1. Communications 2. Trust 3. Responsibility alignment
4. Respect 5. Send value to customer