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
Your Code Sucks: Best Practices for Enterprise ...
Search
Arthur Kay
August 15, 2012
Programming
8
2.6k
Your Code Sucks: Best Practices for Enterprise JavaScript Development
From ThatConference 2012
Arthur Kay
August 15, 2012
Tweet
Share
More Decks by Arthur Kay
See All by Arthur Kay
Analyzing the ROI of JavaScript in Enterprise Software Development
arthurakay
0
140
Debugging your Apps with Google Chrome and Sencha
arthurakay
1
220
Announcing Ext JS 5
arthurakay
0
130
Conquering the Command Line
arthurakay
0
250
The Future of Enterprise App Development
arthurakay
0
120
Best Practices for Enterprise JavaScript Applications
arthurakay
7
2.4k
Bringing the Mobile Web to the Cloud
arthurakay
2
550
Building Native Windows 8 Apps with Sencha
arthurakay
0
240
Creating Windows 8 Apps with Ext JS
arthurakay
1
280
Other Decks in Programming
See All in Programming
Outline View in SwiftUI
1024jp
1
330
シェーダーで魅せるMapLibreの動的ラスタータイル
satoshi7190
1
480
Remix on Hono on Cloudflare Workers
yusukebe
1
300
Functional Event Sourcing using Sekiban
tomohisa
0
100
Why Jakarta EE Matters to Spring - and Vice Versa
ivargrimstad
0
1.2k
CSC509 Lecture 13
javiergs
PRO
0
110
Jakarta EE meets AI
ivargrimstad
0
690
カンファレンスの「アレ」Webでなんとかしませんか? / Conference “thing” Why don't you do something about it on the Web?
dero1to
1
110
どうして僕の作ったクラスが手続き型と言われなきゃいけないんですか
akikogoto
1
120
Streams APIとTCPフロー制御 / Web Streams API and TCP flow control
tasshi
2
350
Ethereum_.pdf
nekomatu
0
470
Macとオーディオ再生 2024/11/02
yusukeito
0
370
Featured
See All Featured
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
232
17k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
26
1.4k
Code Reviewing Like a Champion
maltzj
520
39k
Imperfection Machines: The Place of Print at Facebook
scottboms
265
13k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
506
140k
Six Lessons from altMBA
skipperchong
27
3.5k
The Invisible Side of Design
smashingmag
298
50k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
33
1.9k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
PRO
10
720
Reflections from 52 weeks, 52 projects
jeffersonlam
346
20k
Build The Right Thing And Hit Your Dates
maggiecrowley
33
2.4k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
131
33k
Transcript
Best Practices for Enterprise JavaScript Applications YOUR CODE SUCKS
WHO AM I? • Arthur Kay • Solutions Engineer @
Sencha, Inc. • Web Development ~15 years • www.akawebdesign.com • @arthurakay
AGENDA • Improving application performance • Increasing code stability •
Scaling applications for enterprise • Tools • Advice
None
IMPROVING APPLICATION PERFORMANCE Part 1
CACHING
THIS CODE SUCKS
DO THIS INSTEAD • Cache values (references) • Avoid using
document.getElementById() and other global queries
DO THIS INSTEAD
OVER NESTING
THIS CODE SUCKS
DO THIS INSTEAD • Use lightweight containers (reduce DOM) •
Lazy Rendering
DO THIS INSTEAD
MEMORY LEAKS
THIS CODE SUCKS
DO THIS INSTEAD
INCREASING CODE STABILITY Part 2
SYNTAX ERRORS
THIS CODE SUCKS
DO THIS INSTEAD • Use JSLint (or something else) •
AUTOMATE SYNTAX CHECKING
ONE CLASS PER FILE
THIS CODE SUCKS
DO THIS INSTEAD • Organize your file system • Files
and folders should match namespacing • MVC (or something) • Development loader / Production builder
NAMES HAVE MEANING
THIS CODE SUCKS
DO THIS INSTEAD • Descriptive names on everything (except iterators)
• Common naming conventions (camelCase vs TitleCase vs nocase) • Exceptions for • constants ( SOME_CONSTANT ) • constructors ( MyClass ) • sub-namespaces ( Foo.bar.Class )_
COMMENTS / DOCUMENTATION
THIS CODE SUCKS
DO THIS INSTEAD • Comment top-level structures • Add notes
whenever logic is not obvious • Build your docs into a searchable tool
SCALING APPLICATIONS FOR ENTERPRISE Part 3
AVOID DUPLICATION
THIS CODE SUCKS
DO THIS INSTEAD • Abstraction! • Use mixins when possible
• Apply stuff to prototypes • Have similar classes/methods? • call() and apply()
DO THIS INSTEAD
SMALLER FILES. WHITE SPACE.
THIS CODE SUCKS
DO THIS INSTEAD • Keep methods under 50 lines •
Keep files under 500 lines • Use as much whitespace as possible.
UNIT TESTS
THIS CODE SUCKS
DO THIS INSTEAD • Write “testable” code • Focus on
important / trouble areas • AUTOMATE UNIT TESTING • Don’t insist on UI (integration/iteraction) tests * Test Driven JavaScript Development by Christian Johansen
TOOLS Stuff You Should Know About
IDE
INSPECT ELEMENT
YSLOW
JS DUCK
PHANTOM.JS
ADVICE Things I’ve Learned
SPECIFICATION – NOT TDD
NEVER STOP LEARNING
BREAK (SOME) RULES
None
ADDITIONAL RESOURCES • “Maintainable JavaScript” by Nicholas Zakas • http://www.slideshare.net/nzakas/maintainable-javascript-2012
• “Code Conventions for JS” by Douglass Crockford • http://javascript.crockford.com/code.html • “JavaScript Performance Tips & Tricks” by Grgur Grisogono • http://moduscreate.com/javascript-performance-tips-tricks/
THANKS! Arthur Kay | @arthurakay
SPEAKERDECK.COM/U/ARTHURAKAY Share this presentation: