Sign in to confirm you’re not a bot
This helps protect our community. Learn more

Best of Fluent 2012: Maintainable JavaScript

O'Reilly
198K subscribers
56K views 12 years ago
Video of Nicholas Zakas from his Fluent Conference 2012 Presentation Maintainable JavaScript tackles the difficult problem of writing code as part of a large team. When you're writing code that only you will change, there aren't any issues. As soon as you're writing code that someone else is going to also be changing, you need to think harder about the decisions you make. Will another developer be able to understand what you did? Did you organize your code in such a way that it's easy to adapt and extend? Long after you're gone, will others be able to continue using the same code, or will it need to be rewritten because no one understands it? This session shows the best practices used by teams to ensure their JavaScript is as maintainable as possible. NOTE: To view an HD version go to:    • Best of Fluent 2012: Maintainable - JavaSc...   About Nicholas Zakas Nicholas C. Zakas worked at Yahoo! for almost five years, building and defining fro …...more
...more
These chapters are auto-generated

Intro

0:00

Adaptable

8:50

Style Guide

11:05

Indent

15:13

Acronym

23:09

Programming Practices

24:56

Ghostbusters

25:59

JavaScript in HTML

26:26

Use Templates

27:12

Keep JavaScript in CSS

28:11

Event Handlers

29:50

Overriding Methods

32:46

Throw Your Own Errors

36:00

Bad Checking

38:35

Config Data

40:07

All URLs

40:52

Automation

41:59

Build Processes

42:29

Preprocessor

43:19

Documentation

43:42

YuiDoc

43:57

jslint

44:03

Yui Compressor

44:21

uglifyJS

44:39

closure

44:51

Apache Ant

45:05

Grunt

45:21

Article

45:52

Code Style Guidelines

46:19

Always Code

46:39
Best of Fluent 2012: Maintainable JavaScript
662Likes
56,739Views
2013Apr 26
Video of Nicholas Zakas from his Fluent Conference 2012 Presentation Maintainable JavaScript tackles the difficult problem of writing code as part of a large team. When you're writing code that only you will change, there aren't any issues. As soon as you're writing code that someone else is going to also be changing, you need to think harder about the decisions you make. Will another developer be able to understand what you did? Did you organize your code in such a way that it's easy to adapt and extend? Long after you're gone, will others be able to continue using the same code, or will it need to be rewritten because no one understands it? This session shows the best practices used by teams to ensure their JavaScript is as maintainable as possible. NOTE: To view an HD version go to:    • Best of Fluent 2012: Maintainable - JavaSc...   About Nicholas Zakas Nicholas C. Zakas worked at Yahoo! for almost five years, building and defining front-end strategy for some of Yahoo's largest sites. Nicholas is also the author of several books, including High Performance JavaScript, Professional JavaScript for Web Developers, and Professional Ajax. Don't miss an upload! Subscribe! http://goo.gl/szEauh Stay Connected to O'Reilly Media by Email - http://goo.gl/YZSWbO Follow O'Reilly Media: http://plus.google.com/+oreillymedia   / oreilly     / oreillymedia  

Follow along using the transcript.

O'Reilly

198K subscribers