Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A Public Commitment to Performance

Seth Walker
October 15, 2013
Technology
0
3.7k

A Public Commitment to Performance

Presented at Velocity 2013 NYC.

Seth Walker

October 15, 2013
Tweet

More Decks by Seth Walker

See All by Seth Walker
Performance and Maintainability with Continuous Experimentation
sethwalker
2
1.3k

Other Decks in Technology

See All in Technology
AndroidXR 開発ツールごとの できることできないこと
donabe3
0
130
【Developers Summit 2025】プロダクトエンジニアから学ぶ、 ユーザーにより高い価値を届ける技術
niwatakeru
2
1.4k
管理者しか知らないOutlookの裏側のAIを覗く#AzureTravelers
hirotomotaguchi
2
380
RSNA2024振り返り
nanachi
0
580
PHPカンファレンス名古屋-テックリードの経験から学んだ設計の教訓
hayatokudou
2
260
表現を育てる
kiyou77
1
210
偶然 × 行動で人生の可能性を広げよう / Serendipity × Action: Discover Your Possibilities
ar_tama
1
1.1k
AndroidデバイスにFTPサーバを建立する
e10dokup
0
250
Amazon S3 Tablesと外部分析基盤連携について / Amazon S3 Tables and External Data Analytics Platform
nttcom
0
130
自動テストの世界に、この5年間で起きたこと
autifyhq
10
8.5k
レビューを増やしつつ 高評価維持するテクニック
tsuzuki817
1
710
エンジニアのためのドキュメント力基礎講座〜構造化思考から始めよう〜（2025/02/15jbug広島#15発表資料）
yasuoyasuo
17
6.7k

Featured

See All Featured
The Invisible Side of Design
smashingmag
299
50k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.1k
Done Done
chrislema
182
16k
Typedesign – Prime Four
hannesfritz
40
2.5k
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
6
550
The Art of Delivering Value - GDevCon NA Keynote
reverentgeek
10
1.3k
RailsConf 2023
tenderlove
29
1k
Optimising Largest Contentful Paint
csswizardry
34
3.1k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
32
2.1k
Product Roadmaps are Hard
iamctodd
PRO
50
11k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
44
7k
Six Lessons from altMBA
skipperchong
27
3.6k

Transcript

  1. A Public Commitment to Performance One weird trick to kickstart

    a performance culture Velocity NYC October 15, 2013

  2. @sethwalker

  3. None

  4. http://bit.ly/performanceculture

  5. Who is responsible for performance?

  6. None

  7. You need a performance culture

  8. Changing culture is hard

  9. One weird trick

  10. Etsy -2years

  11. What we had

  12. What we wanted

  13. Weather report

  14. None

  15. Choosing metrics

  16. Key pages

  17. 95th percentile backend

  18. Weekday

  19. or whatever...

  20. Keep it simple

  21. You can change it later

  22. You can change it later

  23. You will change it later

  24. Get your tools in place

  25. Can you measure it?

  26. Repeatable?

  27. None

  28. Woah, embarrassing

  29. It's not as private as you might think

  30. This motivates your team to get better

  31. Consider your audience(s)

  32. Community Engineering Team Velocity

  33. Woah, embarrassing

  34. Numbers are boring

  35. None

  36. Graphs are awesome

  37. None

  38. Celebrate wins

  39. Performance is invisible

  40. None
  41. None
  42. None

  43. Ongoing context

  44. Context for regressions

  45. None

  46. Iterate

  47. Graphs are awesome

  48. None

  49. What's next

  50. One weird trick

  51. Take the long view

  52. A note about privilege

  53. "I love, love, love the latest performance report -- the

    report itself, not just the great numbers." - Etsy CEO Chad Dickerson

  54. Tell them I said it is all good.

  55. Now, you share

  56. Questions? http://bit.ly/performanceculture @sethwalker