Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Speaker Deck
PRO
Sign in
Sign up for free
Front-End Ops - jQuery Conf Chicago 2014
Alex Sexton
September 13, 2014
Technology
1
960
Front-End Ops - jQuery Conf Chicago 2014
Alex Sexton
September 13, 2014
Tweet
Share
More Decks by Alex Sexton
See All by Alex Sexton
Your Very Own Component Library
slexaxton
5
680
Hacking Front-End Apps
slexaxton
4
2.1k
Practicing Safe Script
slexaxton
18
2.4k
Other Decks in Technology
See All in Technology
ロボットの実行すらメンドクサイ!?
kou12092
0
120
Oracle Cloud Infrastructure:2022年7月度サービス・アップデート
oracle4engineer
PRO
0
170
A3-1 IBM Championが本音で語る「IBM Cloud」
kolinz
0
300
Microsoft Data Analytics trends : ”Lakehouse” , ”Data Mesh"
ryomaru0825
2
120
AlexNet前夜
yushiku
PRO
0
740
20220728_新資格『SAP on AWS - Specialty 認定』ってどんな資格?/about-SAP-on-AWS-Specialty
emiki
1
420
DMMプラットフォーム ゼロから始めるKubernetes運用 課題と改善
pospome
0
390
Istioを活用したセキュアなマイクロサービスの実現/Secure Microservices with Istio
ido_kara_deru
3
380
eBPFで実現するコンテナランタイムセキュリティ / Container Runtime Security with eBPF
tobachi
PRO
5
1.6k
CloudWatchアラームによるサービス継続のための監視入門 / Introduction to Monitoring for Service Continuity with CloudWatch Alarms
inomasosan
1
410
〇〇みたいな検索作ってと言われたときに考えること / thinking before developing search system like that one
ryook
5
2.6k
サイバー攻撃を想定したクラウドネイティブセキュリティガイドラインとCNAPP及びSecurity Observabilityの未来
syoshie
1
1k
Featured
See All Featured
Making Projects Easy
brettharned
98
4.4k
The Invisible Side of Design
smashingmag
290
48k
The Web Native Designer (August 2011)
paulrobertlloyd
75
2k
How GitHub Uses GitHub to Build GitHub
holman
465
280k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
21
1.4k
StorybookのUI Testing Handbookを読んだ
zakiyama
6
2.5k
ParisWeb 2013: Learning to Love: Crash Course in Emotional UX Design
dotmariusz
100
5.9k
Thoughts on Productivity
jonyablonski
44
2.4k
What's in a price? How to price your products and services
michaelherold
229
9.4k
What's new in Ruby 2.0
geeforr
335
30k
Debugging Ruby Performance
tmm1
65
10k
How to name files
jennybc
40
63k
Transcript
Front-End Ops Alex Sexton | 2014
None
A little under a year later…
None
Naming Things #hardCSproblems
Regressive Enhancement
Polyfill
Prollyfill
None
None
Parlayfill
Mollyfill
ANYWAYS
Front-End Ops Alex Sexton | 2014
FEO
UGLY (in spanish)
FeOps
None
Iron Ops catchy
I pay the Iron Price for lower latency
What is Front-End Ops?
None
“Some weird terms you invented to describe things that don’t
exist.” - John Edgar, Digital Ocean
None
First Of All
More Importantly…
That’s the whole point.
Serving webpages is really hard.
that’s why we have conferences for this stuff (jQConf, FEOpsConf)
Conferences That Don’t Exist
HTML &ENTITY; CONF
SundayMorningConf
Front-End Ops is the collection of things you can do
to make serving webpages easier. opposite of harder
So you can focus on your product.
None
Mature FEOps benefits the people who don’t have time to
think about this stuff.
Lots of folks agree!
So really what is it?
The App Everything Else
The App Everything Else FEOps™
Article Recap
“Front-End Ops Engineers are the bridge between an application’s intent
and an application’s reality”
Why?
We’re collectively insane.
None
Why now?
Application logic is being deferred to the client side.
Performance Testing
Error Logging
Lifecycle Logging
Measurement over time
A Front-End Ops Engineer enables long-term progress
Performance is the foundation on which user experience is built.
A UX in the DOM is worth two on the
wire.
Speed is the metric that we measure by.
Speed of app.
Speed of tools.
Speed of development.
None
(all of these can be measured and tracked)
(all of these can be measured and tracked) ((but it’s
important to read the data right))
Speed of app.
Speed up your app In 5 Simple Steps How To
Step 1 forget everything you know because it’s wrong
Step 2 it’s probably the network
Step 3 Probably Read Ilya’s book
Step 4 measure
Step 5 measure
1) Forget everything 2) It’s probably the network 3) Ilya’s
book 4) Measure 5) Measure Recap
Chrome DevTools Flame Graphs, CPU Profiles, and Repaints/Reflows info are
invaluable.
The limiting factor of your system should be the speed
of light. Assuming you have Fiber
0 50 100 150 200 THEORETICAL GRAPHS
OS X Android iOS Blackberry 1200ms 0ms
1200ms 0ms
1200ms 0ms
Distribution of Load Time
Desktop Mobile
Two distinct loading curves
What you see when you add them together.
ಠ_ಠ
Measurement
Measurement
If I had to pick one part that was most
important to FEOps, it’d be all of it
but #2 would be MEASUREMENT
Measure twice. Optimize once.
Make a dashboard.
Things you can put in a dashboard
Speed Index Over Time
Speed Index Over Time And then draw lines where commits
happen.
Speed Index Over Time And then draw lines where commits
happen. And then link to the diff between tests
image is of speedcurve.com
Things you can put in a dashboard
Page Weight Over Time
Page Weight Over Time gzipped/ungzipped
Page Weight Over Time gzipped/ungzipped Broken down by filetype
Requests Over Time 0E+00 2.5E+01 5E+01 7.5E+01 1E+02
Errors There are lots of great companies that will help
you do this these days.
Build Time Over Time
Speed of tools. usually build
Rule #1
The time between making a change, and seeing it in
your app must approach 0.
Rule #2
Never do anything twice.
AKA “Cache Everything”
(feel free to do two things at the same time
though)
Speed of development.
Speed of development. AKA Developer Happiness
Spare no expense.
Take the time to make source maps work.
There should be one easy command to get everything to
work.
There should be one easy command to get everything to
work. Vagrant can help with environments
Turn on LiveReload
Implement Lifecycle Logging
Set a calendar reminder to update your dependencies
Have a rigorous Style Guide that everyone follows, and that
robots yell about. Lint!
If we take care to build robust tools around these
FEOps ideals, ! developers will need to master less, and will be able to focus on users more.
None
Let’s make fast, measurement driven, easily-maintained web applications the starting
point.
Thanks @slexaxton