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
730
Hacking Front-End Apps
slexaxton
3
2.4k
Practicing Safe Script
slexaxton
18
2.8k
Other Decks in Technology
See All in Technology
アプリケーションの中身が見える!Mackerel APMの全貌と展望 / Mackerel APMリリースパーティ
mackerelio
0
450
Data Hubグループ 紹介資料
sansan33
PRO
0
1.7k
テストを実施する前に考えるべきテストの話 / Thinking About Testing Before You Test
nihonbuson
PRO
14
2k
MCP Clientを活用するための設計と実装上の工夫
yudai00
1
810
オープンソースのハードウェアのコンテストに参加している話
iotengineer22
0
600
All About Sansan – for New Global Engineers
sansan33
PRO
1
1.2k
データプレーンプログラミングとは? DPU&スイッチASICの開発経験から語る
ebiken
PRO
1
260
他チームへ越境したら、生データ提供ソリューションのクエリ費用95%削減へ繋がった話 / Cross-Team Impact: 95% Off Raw Data Query Costs
yamamotoyuta
0
240
CloudBruteによる外部からのS3バケットの探索・公開の発見について / 20250605 Kumiko Hennmi
shift_evolve
3
160
2025advance01
minamizaki
0
130
Contract One Dev Group 紹介資料
sansan33
PRO
0
6k
OSMnx Galleryの紹介
mopinfish
0
150
Featured
See All Featured
Responsive Adventures: Dirty Tricks From The Dark Corners of Front-End
smashingmag
252
21k
VelocityConf: Rendering Performance Case Studies
addyosmani
329
24k
Why You Should Never Use an ORM
jnunemaker
PRO
56
9.4k
The Language of Interfaces
destraynor
158
25k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
19
1.3k
Bash Introduction
62gerente
614
210k
Build your cross-platform service in a week with App Engine
jlugia
231
18k
Stop Working from a Prison Cell
hatefulcrawdad
269
20k
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
47
2.8k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
6
660
Scaling GitHub
holman
459
140k
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