2011 jQuery Summit, here I come!


Earlier this month, I spoke at the Boston jQuery Conference, where my talk on “Plugin Authoring Best Practices” was well received. It went so well that I’m going to be giving it talk again, but this time online, at the jQuery Summit!

Like last year, I’ll be giving two talks. On the first day, I’ll be giving the aforementioned Plugin talk. On the second day, I’ll be giving a talk on JavaScript Unit Testing with QUnit.

Continue on for more information about my talks and a 20% off coupon code!

Here’s are my talk abstracts:

Plugin Authoring Best Practices

jQuery plugins are everywhere, and the chance that YOU will write one—if you haven’t already—are pretty high. It might start with a little bit of functionality that you want to reuse or share with someone else, but before you know it… you’ve released dozens of jQuery plugins and you’re writing articles and giving presentations on jQuery Plugin Authoring Best Practices at conferences…. Ok, maybe that’s just me.

Regardless, there are many techniques you should know for writing your own reusable jQuery code, or “jQuery plugin,” in a way that makes it feel like a natural extension of jQuery.

In this talk, you’ll learn how to create custom selectors, chainable methods that double as getters and setters, and traversal or filtering methods that are .end()-able. You’ll learn how to organize your code in IIFEs and namespaces, extend option defaults, and even create a custom package.json for your plugin, so that it can be submitted to the upcoming jQuery plugins index.

JavaScript Unit Testing with QUnit

You’ve been told that you should be unit testing your JavaScript, but like most developers, you have some questions that need to be answered first. What is a unit test? Why should I unit test my code? How do I actually write unit tests? Are there any best practices I should know about?

In this talk, you’ll get answers to those questions from somebody who has written unit tests for jQuery and dozens of jQuery plugins. You’ll get an in-depth explanation of QUnit, the easy-to-use JavaScript test suite used and maintained by the jQuery project. You’ll learn the difference between assertions and expectations, why tests should be atomic, and how to utilize fixtures and mock AJAX requests.

Most importantly however, you’ll learn why you should be writing unit tests in the first place!

For more information or to register for the conference, visit the jQuery Summit website, and don’t forget to use coupon 20COWBOY for a 20% discount!

Post A Comment

  • Any of these HTML tags may be used for style: a, b, i, br, p, strong, em, pre, code.
  • Multi-line JavaScript code should be wrapped in <pre class="brush:js"></pre>
    (supported syntax highlighting brushes: js, css, php, plain, bash, ruby, html, xml)
  • Use &lt; instead of < and &gt; instead of > in the examples themselves.