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
Front-End Ops - jQuery Conf Chicago 2014
Search
Alex Sexton
September 13, 2014
Technology
1
1k
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
740
Hacking Front-End Apps
slexaxton
3
2.4k
Practicing Safe Script
slexaxton
18
2.9k
Other Decks in Technology
See All in Technology
PdM業務における使い分け
shinshiro
0
590
ML Pipelineの開発と運用を OpenTelemetryで繋ぐ @ OpenTelemetry Meetup 2025-07
getty708
0
250
スプリントゴール未達症候群に送る処方箋
kakehashi
PRO
1
200
QAを早期に巻き込む”って どうやるの? モヤモヤから抜け出す実践知
moritamasami
2
180
Talk to Someone At Delta Airlines™️ USA Contact Numbers
travelcarecenter
0
170
怖くない!GritQLでBiomeプラグインを作ろうよ
pal4de
1
120
エンジニアリングマネージャー“お悩み相談”パネルセッション
ar_tama
1
660
増え続ける脆弱性に立ち向かう: 事前対策と優先度づけによる 持続可能な脆弱性管理 / Confronting the Rise of Vulnerabilities: Sustainable Management Through Proactive Measures and Prioritization
nttcom
1
170
An introduction to Claude Code SDK
choplin
3
3.3k
ゼロから始めるSREの事業貢献 - 生成AI時代のSRE成長戦略と実践 / Starting SRE from Day One
shinyorke
PRO
0
230
経験がないことを言い訳にしない、 AI時代の他領域への染み出し方
parayama0625
0
150
室長の逆襲 :データ活用の陣地を増やすためのヒント
masatoshi0205
0
180
Featured
See All Featured
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Making Projects Easy
brettharned
116
6.3k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
10
990
A designer walks into a library…
pauljervisheath
207
24k
Automating Front-end Workflow
addyosmani
1370
200k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
357
30k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Fireside Chat
paigeccino
37
3.5k
Agile that works and the tools we love
rasmusluckow
329
21k
GitHub's CSS Performance
jonrohan
1031
460k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3.1k
Faster Mobile Websites
deanohume
308
31k
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