Author Archives: Ben Teese

About Ben Teese

I'm a Senior Consultant at Shine Technologies. You can find me on Twitter and GitHub.

Backbone Boilerplate Vs. Rails Asset Pipeline

We recently shifted from Backbone Boilerplate to the Rails Asset Pipeline for generating the various assets (Javascript, CSS, HTML, images, etc) that comprise teamstuff.com, a single-page app. In this post I’ll talk about our motivations for making the shift, what we had to change to get … Continue reading

Posted in AJAX, Javascript, Tools, UI | Tagged | 3 Comments

Amazon Web Services Publish a Case Study on Shine in the Cloud

Into things Cloud-related? Amazon Web Services have just posted a case study on how Shine (yes, that’s us) is migrating mission-critical installations of our products from customer’s on-site infrastructure to the cloud. It also covers how Shine has used RDS … Continue reading

Posted in Uncategorized | Leave a comment

JSConf Down Under: A Conference Report

I attended JSConf Down Under yesterday. The conference format was quite straightforward: one day, one stream, nine speakers. In this post I’ll talk about the three things at the conference that had the biggest impression on me: Brendan Eich’s presentation … Continue reading

Posted in Javascript, Opinion | Tagged | 2 Comments

Efficient Stateful Views With Backbone, Part 2: Collections & Animations

In Part 1 of this blog series, we saw how UI state could be maintained efficiently in a Backbone app by introducing view-management infrastructure and retaining references to views. In Part 2, I’m going to talk about how this strategy … Continue reading

Posted in AJAX, Javascript, UI | Tagged | 2 Comments

Efficient Stateful Views with Backbone.js, Part 1

One of the good things about single-page apps is that it’s possible for them to remember UI state within a page. If an area of the page is hidden from the user, and then redisplayed later, you’re able to display … Continue reading

Posted in AJAX, Javascript, UI | Tagged | 5 Comments

Javascript Module Loading + Shared Namespaces = Badness

Both module loaders and shared namespaces are valid techniques for modularising your JavaScript code. However, doing both at the same time is a recipe for difficult-to-track defects.

Posted in Javascript | 1 Comment

On Pair Programming

Working on a project that used pair programming was something that I’d wanted to try for a long time but had never had the opportunity to do. Consequently, when a chance came up to work on a project where the … Continue reading

Posted in Agile, Opinion | Tagged , | Leave a comment

How to Stop Cucumber Becoming Technology Roadkill

I’ve worked on a number of projects with Cucumber now, and I think it is a terrific tool. However, I’ve been seeing it used in ways that it was not originally intended for, the consequence being acceptance-test suites that grow … Continue reading

Posted in Testing, Tools | Tagged , | 1 Comment

Building a shared calendar with Backbone.js and FullCalendar: A step-by-step tutorial

In a prior post, I explained how Backbone.js can be used to implement cascading select boxes. However, this was pretty much just a read-only affair, and these were relatively simple HTML elements. How does Backbone fare creating, updating and deleting … Continue reading

Posted in AJAX, Javascript | Tagged , , | 35 Comments

Cascading Select Boxes with Backbone.js: A Step-by-Step Tutorial

Up until recent years, client-side Javascript development has resembled the wild-west from a software design perspective. Libraries like jQuery have certainly helped, but with the rise of Single-Page Applications, jQuery alone doesn’t provide enough of an overall framework for large-scale … Continue reading

Posted in AJAX, Javascript | Tagged | 20 Comments