Tuesday, December 8, 2015

JSConf Last Call 2015

I gave a 1/2 hour talk at JSConf Last Call 2015 on December 6, 2015 title "Treating Framework Fatigue With JavaScript. The gist of the talk is that in today's world of never ending new frameworks, it's critically important to have a solid foundation in the JavaScript language in order to cut through the hype and understand how these frameworks do their thing.

I've been speaking at my local meetup group, of which I'm now the organizer, for the past year or so but this was my first time speaking at a conference. I'm looking forward to doing more conference speaking, as I really enjoyed the experience and had some very positive feedback on my talk! If you're a conference organizer, or know someone who is, please feel free to put my name on the radar.

Tuesday, December 1, 2015

Organizing a Meetup Group

I recently took over as organizer of the Santa Barbara JavaScript Meetup after functioning as acting organizer for the past year. It's a great way to network and meet like-minded people in the local tech community.

I've had a good run of increasingly successful and well-attended events, and am looking forward to keeping the momentum going in the coming year.

I've reached out to my my employer about sponsoring the Meetup, and will reach out to other local tech companies also, in hopes that we can afford to bring in visiting speakers and host more elaborate events in the future.

Exciting times, to be sure, and I'd love feedback and suggestions from other Meetup organizers on what makes for a successful group!

ECMAScript 6 In Depth: Part III

The conclusion of the epic trilogy of talks I gave at the Santa Barbara JavaScript Meetup on August 18th, 2015.

Thursday, June 25, 2015

ECMAScript 6 In Depth: Part II

Part two of a planned three-part talk I gave at the Santa Barbara JavaScript Meetup on June 23rd, 2015.

The recorded presentation is available here. (you'll need to download it to watch past the first 15 minutes)

Saturday, June 20, 2015

ECMAScript 6 In Depth: Part I


Part one of a planned three-part talk I gave at the Santa Barbara JavaScript Meetup on May 21st, 2015.

The recorded presentation is available here. (you'll need to download it to watch past the first 15 minutes)

Part II is coming up Tuesday, June 23rd:

Friday, May 1, 2015

2015 Fluent Conference Recap


A talk I gave April 30th, 2015 to the Santa Barbara JavaScript Meetup, based on my experience at Fluent and the sessions I attended. There were so many more that I couldn't attend.

Thursday, August 7, 2014

Santa Barbara JavaScript Meetup

I gave a well-received talk on Yeoman to the Santa Barbara JavaScript Meetup crowd on Wednesday night, hosted by Agilysys. Based on the positive feedback, we'll definitely host more.

Wednesday, September 4, 2013

Ember 1.0

Earlier this year I was evaluating Ember.js along with several other frameworks/libraries for some projects at work. At the time, pre-1.0, I found Ember promising but frustrating due to its steep learning curve, frequent breaking changes and documentation that was inadequate and out-of-sync with the codebase. Still, I found much to admire in Ember's approach, as I noted in a previous post.

One thing that struck me almost immediately was a strong push back from the Ember principals against AMD. The most prominent example was Tom Dale's blog post 'AMD is Not the Answer', which drew some impassioned responses including this one and this one from RequireJS creator James Burke. Having incorporated AMD into my toolbox early on, I find the necessary boilerplate a very reasonable tradeoff in return for concise modules with explicitly stated dependencies, available in the browser.

You can imagine my surprise confusion amusement then, when I read the Ember 1.0 announcement the other day and found this gem:

Today, tools like require.js and module systems like AMD, Node, and ES6 Modules continue to gain traction. Increasingly, people are using named modules and module loaders rather than storing their code in globals.

To prepare for this future, all of the code lookup and naming conventions in Ember.js now go through a single Resolver. The default Resolver still looks for code under global namespaces, but Ember App Kit already provides an alternative resolver that looks for code in AMD modules.

This quote from the Ember official blog is actually a little misleading. A closer look at the Ember App Kit reveals that it supports ES6 module syntax, which is then "transpiled" to AMD syntax via the ES6 module transpiler. Still, this is a far cry from Tom's blog post and likely reflects the widespread adoption of AMD in the developer community around Ember.

With Ember reaching 1.0 status as of August 31, I'm taking another look to see if the stability, module support, and documentation have improved. I'll build out a demo app with the same Youtube emulator domain as other recent demos for side-by-side comparison of a fairly simple but non-trivial example application across frameworks/libraries. I'll post the source on github and link here when it's done.

Tuesday, September 3, 2013

Nexus 7

So I finally bit the bullet and bought a tablet. After hanging back looking at various offerings I decided to get the new Nexus 7 from Google/Asus, mainly for its combination of low price point and excellent reviews/features.

I bought it mainly for fun/casual use but want to tinker a little also, so I paired the Nexus 7 with a Microsoft Wedge bluetooth keyboard and mouse, and installed the kWS Android web server and DroidEdit so I can do bare-bones web development right on the tablet.

I've only had the device for a few days and am still finding my way around, but so far I'm pretty happy. I'll try to post a detailed review soon.

Friday, August 16, 2013

Aura.Backbone.YouTube

Continuing with my theme of demo projects built on a common problem domain - a bare-bones YouTube emulator - I decided to dive into Aura.js http://aurajs.com. Aura is a "clean and scalable architecture for complex JavaScript applications" that evolved from ideas put forth by Googler Addy Osmani and former Yahoo Nicholas Zakas . It provides a high-level component-based abstraction with focus on sandboxing and inter-component communication via publish/subscribe. Aura is framework-agnostic, so you can plug in popular tools like Backbone, Angular, Ember, etc. For the demo I plugged in the ever popular Backbone library.

View the demo here http://tdoherty.github.io/aura.backbone.youtube/

View the source on github:

aura.backbone.youtube
https://github.com/tdoherty/aura.backbone.youtube
aura.backbone.youtube - An Aura.js demo using Backbone.js and YouTube APIs

Friday, April 19, 2013

"OOP to me means only messaging, local retention and protection and hiding of state-process, and extreme late-binding of all things. It can be done in Smalltalk and in LISP. There are possibly other systems in which this is possible, but I’m not aware of them."

~Alan Kay

So my colleagues and I were having a discussion about object oriented programming (OOP) and exactly what it means today versus when the term was first coined by Alan Kay in the late 60’s. Specifically, whether prototype-based languages are truly object oriented as compared to class-based languages which are the mainstream. It’s very interesting to read Kay’s own take on the subject, and realize that what most of us consider to be OOP today resembles but little the original conception.


image

Tuesday, April 2, 2013

Backbone Boilerplate

I wrote a rough demo with Tim Branyen’s Backbone Boilerplate using YouTube data feeds. It’s a work in progress as I’m learning Backbone Boilerplate and its bundled LayoutManager.

Check out the demo here


Backbone-Boilerplate.YouTube
github.com

image

Wednesday, March 13, 2013

AngularJS

I wrote a rough demo with Google’s AngularJS using YouTube data feeds. It’s a work in progress as I’m learning Angular.

Check out the demo here


Angular.YouTube
github.com

image

Friday, March 8, 2013

jQuery.SpinJS

I created a jQuery plugin wrapping Felix Gnass’ excellent spin.js. The plugin adds a background div with configurable color and transparency, and supports AMD. Check it out and let me know what you think.


jQuery.SpinJS
github.com


image

Monday, March 4, 2013

Client Side JavaScript MV* With Ember.js

My team at work is evaluating the suitability of several tools for client-side application development. We’re looking at building out some non-trivial applications on the client and wanted to make the best collective, educated decision on the best tool(s) for the job.

The tools we’ve been looking at include:

  • Backbone

  • Knockout

  • Angular

  • Ember

Backbone


I’ve already grown pretty familiar with Backbone, having spearheaded its adoption into our tools set a year or so ago. We’ve built out a few non-trivial applications with Backbone and admire it’s simplicity and elegance. Backbone is lean and non-prescriptive, it’s a minimalistic library that gives you the most basic structure and tools for event-based model management.

Monday, February 27, 2012

Twirl Your Mustache

Reuse Templates On The Client And Server With CouchDB, CouchApp, and Mustache

In my last post I talked about my introduction to building applications with Apache CouchDB and CouchApp. I’ve been refactoring the app to use Backbone.js and RequireJS on the client, and to take advantage of templating to make presentation logic more DRY. This post shows how to reuse Mustache templates on the client and server using CouchDB and CouchApp. I’ve left out the Backbone/RequireJS code for simplicity, and illustrate the client code using jQuery’s shorthand ‘$.get’ AJAX method.

Mustache is a logic-less templating language available for a variety of languages. It ships with CouchApp, and Backbone is agnostic, so it seemed a no-brainer. Mustache supports partial templates, for portions of a page’s markup, and I’ll show how to reuse a partial template to do a partial page refresh on the client.

Say we have the following extremely simplistic template:

/templates/page.html:

Partial templates are indicated with the greater than (‘>’) symbol, so here we’re indicating that a partial template named ‘content’ should be rendered in the <div id=”content”> element. Now let’s say we have the following partial template:

/templates/partials/content.html:

For the server side, we can render HTML pages via CouchDB ‘shows’ and use Mustache in the show code, i.e.:

/_shows/page.js:

Here, this.templates refers to the current design document’s ‘templates’ property, and this.templates.partials to its ‘templates.partials’ property. These correspond to your CouchApp’s directory structure prior to push.

We can then hit the page at: /dbname/_design/docname/_show/page, and use a combination of rewrites.json and a proxy or virtual host to pretty up the URL.

For our purposes, we’re considering reusing a template from the ‘partials’ directory for a client-side partial page refresh. We can serve the template markup from a show also, passing the template name in the URL, i.e., /dbname/_design/docname/_show/templates/page.html:

/_shows/templates.js:

Here, we first look for the template name in the design doc’s templates, then in templates.partials.

On the client, we’ll use the jQuery plugin for mustache, which ships with CouchApp:

<script src=”vendor/couchapp/jquery.mustache.js”></script>

First we’ll make a GET request for the template:


Then for a partial refresh, we’ll GET our updated data and apply the same partial template on the client:


This is an extremely simplistic example, the point being to illustrate the considerable DRY we can achieve through template reuse. Write the template once, and use it on both the client and server.

Nice!

Thursday, February 16, 2012

Relax, or, adventures with CouchDB for fun and profit.

My employer is pretty cool about allowing devs freedom in choosing tools. They also support R&D-based “play time” to explore new technologies as they pertain to our problem domains. I’ve had a great time over the past year and half specializing in JavaScript development using tools like Backbone.js, RequireJS, Node, etc., while continuing full-stack development for the enterprise.


Recently I got the opportunity to use CouchDB for a customer-facing project. Before he left to pursue greener pastures, our former Development Director authored a conference registration site using CouchDB and CouchApp. Since I’ve earned the “JavaScript Guy” moniker here, I was presented the opportunity of taking over the app for this year’s conference.


Apache CouchDB is a document-oriented database that can be queried and indexed using JavaScript in a MapReduce fashion. CouchDB provides a RESTful JSON API than can be accessed from any environment that allows HTTP requests. CouchApps are JavaScript and HTML5 applications served directly from CouchDB. Assuming your application can fit into those constraints, then you get CouchDB’s scalability and flexibility “for free” (and deploying your app is as simple as replicating it to the production server).


CouchDB represents a significant paradigm shift coming from a relational SQL background. It is extremely flexible as a document store, it is ad-hoc and schema-free, and provides powerful incremental peer-based replication for distributed storage. Like all NoSQL databases, it is not intended as a panacea, nor intended as a substitute for relational databases. It is simply another available tool to evaluate based on a project needs basis.


This project also gave me some exposure to nginx, which is used as a proxy to CouchDB, and Python, which is used for some administrative features behind the scenes.


It’s been pretty awesome getting to know CouchDB, and adding it to my tool belt for consideration on future projects. I’ll try to post more specifics as time permits.