Best of Fluent 2012: Maintainable JavaScript



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: http://youtu.be/nZihjH6_Qns

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
https://www.facebook.com/OReilly


Original source

42 thoughts on “Best of Fluent 2012: Maintainable JavaScript

  • November 4, 2017 at 23:57
    Permalink

    The XMLHttpRequest name feels wrong no matter how you write it.

    Xml? Who capitalizes Xml? Ok, all caps then, like in the wild
    But how about the Http part then? If we put it all caps the reader will lookup for the new XMLHTTP protocol. We need to separate it somehow. Underscore? Well yes, but we use underscore for separating words in variable names. 

    There is absolutely no way to win this. Only by completely changing the object name. But how could you name the object of an XML HTTP request? ARGH!

  • November 4, 2017 at 23:57
    Permalink

    Thats one thing that makes Java and class based languages better than Javascript. If someone overrides a method in Javascript it can take days to figure out the bug. However in Java its only a matter of seconds to find incompatible overrides due to compile time checking.

  • November 4, 2017 at 23:57
    Permalink

    I too like Nicholas Zakas, both his writing and speaking. No pun intended, but I find his speech very fluent, and the combination with his profound knowledge makes it awesome.

  • November 4, 2017 at 23:57
    Permalink

    I like Nicolas Zakas’ talks a lot, because they are densely informational and I always take a lot out of them. What I don’t like about them is N. Zakas’ often embarassing attempts at humor (which – admittedly – mostly suffer from the moody reactions of the respective ,crowd’ he’s speaking to).
    In this one however, he seems much more relaxed and does not try to enforce laughs, which made the whole talk not only informative, but also very entertaining and even funny.

  • November 4, 2017 at 23:57
    Permalink

    Yes i mean it. we must kill the bad fat and belly first to get the 6 pack.

    Listen to this I saw an interview with body building champion where he talks about 7 odd foods he eats to keep his abs hard.

    have a look here bit.ly/19cFq2R?=plrwo

  • November 4, 2017 at 23:57
    Permalink

    Hey RO2player, why don't you join the rest of us in the wonderful world of 'check the description for the HD link' before posting a comment that already has been addressed? Go on, try it, you might like it.

  • November 4, 2017 at 23:57
    Permalink

    Try to maintain the size of your Javascript to zero bytes. It's the best choice unless you want popups on your site, you don't need and/or want it.

  • November 4, 2017 at 23:57
    Permalink

    okthoajjavaentetrwhatwmownmaniowomwei0j3923i39082948384384934902048902q8+(4093mipwjofeiof)(fijckjkljdjwweofmariojwiojfiojewwahowhwfiowejfeijeiorjocldjkljahamenteryhahepjwpjsjwijiwj3i9eiji3j4ioj34j3wejt-t=e.

  • November 4, 2017 at 23:57
    Permalink

    I am new to Javascript coding and thought this was a great video!

    I have a question though.

    At 30:00 it says to keep css style out of Javascript. How would one manipulate the css style of an html element then?

    Example code:
    jsfiddle.net/5Ba2u/

    How would the above be done for better coding practice?
    Thanks in advanced.

  • November 4, 2017 at 23:57
    Permalink

    I assume you're referring to the fact that Pi is all caps? All of the Math constants are capitalized, following the general practice of capitalizing constants (the slide following camel casing).

  • November 4, 2017 at 23:57
    Permalink

    I'd just like to state for the record that "Id" is not an acronym, its an abbreviation. It means "Identification" or "Identifier", not like "I-Dentifier". So capitalizing both letters would be incorrect.

  • November 4, 2017 at 23:57
    Permalink

    Hey Oreilly Media, why don't you join the rest of the us in the wonderful world of 'at least' 720p? Go on, try it, you might like it.

  • November 4, 2017 at 23:57
    Permalink

    I once had a 45 minute argument about whether or not JSLINT errors should break our jenkins build. Though the style itself doesn't effect the program, it was a good way to enforce our style guide. Any thoughts?

  • November 4, 2017 at 23:57
    Permalink

    Harshed word I heard was crap and I don't view that as an expletive. I do however view IE as an expletive if it refers to any version before 10.

  • November 4, 2017 at 23:57
    Permalink

    LOL, 9:25 "Debuggable… which is not a real word… btw… According to M$ word anyway." I can't tell if he was telling a joke there or not.

  • November 4, 2017 at 23:57
    Permalink

    This is a great video. JavaScript doesn't allow you to really split your programming patterns but this video gives you simple tips on how to understand and maintain JavaScript code better.

Leave a Reply