I’m in the middle of a few different projects right now, and, as inevitably happens when attempting to focus on more than one thing, I’m just a tiny bit distracted. Currently, I am:
- Updating the jQuery Columnizer plugin to include the latest requests
- Building Listotron
- Building WelcomeToYourMac
- Updating the layout/plugins of this site
Add into that my the normal responsibilities of work, church, and family (and multiply the family line-item by 2 to properly account for my two year old daughter), and you’ve just about summed up my current ambitions.
Recently I’ve made a fair amount of progress on #5, but at the expense of just about everything else. And while updating this site can be fun, I’d hardly call it productive in the true sense of the word. And so all of this brings me to this post – focus. Not wanting to throw anything off the boat, I’ve instead decided to rotate my attention to a specific task each month.
Since Google Analytics tells me you’re much more interested in the MVC and Columnizer more than any of the other items, in the coming month I’m going to focus in earnest on the the MVC tutorial (with Columnizer next in queue), but before I switch gears I’ve made some moderately exciting progress on the Listotron front that I want to share. It’s completely altered my development plan – more specifically my testing plan – for Listotron.
Absolutely any error that the user runs into, I’ll be able to write a duplicate functional test for exactly that workflow. For any “standard” web app that works over multiple page loads, testing a user path would be tedious and near impossible. Tools like Selenium and SilkTest get of most of the way there, but with a properly engineered AJAX application, we can test just as much with fewer dependancies on other tools.
And I’m a big fan of using fewer tools to accomplish the same ends. Less stuff to do during development decreases cycles spent on process and increases cycles spent on actual development.
I already have a prototype of the Listotron UI running alongside some basic unit tests, but it still needs a bit of code cleanup before I won’t be embarrassed to have others look at it. Expect a full code release and walkthrough in the coming weeks.