walkah: striving towards mediocrity

This year promises to be an exciting one - and one that proves to be full of changes galore. As I mentioned in my last post, much of my 2010 change began late in 2009.

Cue the Bowie...

Leaving Lullabot

Although it's been largely quiet (and really not a huge deal), before the rumours spread too far: I've left my position as the Director of Education for Lullabot. I'm leaving behind a totally awesome team and a wonderful job (in the midst of a recession). Why on earth?!

Let me be very clear: Lullabot isn't in danger, stopping Drupal training, nor is there any backroom drama. The 'bots are wonderful people and chances are very good that we'll continue to collaborate in the future (at the very least, there's still hugs).

This was a very personal decision - and one that was a long time coming. For the morbidly curious, it boils down to three things (and those of you who know me well, know it always comes down to three things):

Travel: Anyone who is friends with a 'bot on Dopplr or Tripit knows that the job entails a lot of time on the road. With over 230 days on the road in the past 2 years, I needed and my kids deserved a break. While we (Lullabot and I) largely worked around this - it's still just part of the gig.

Drupal: I stood up in front of a rather large group of Drupal folks almost a year ago and explained why I hate Drupal - so it's obvious, right? While I feel the points I tried to make still face the community at large (such as smallcore/drupal is not a product, or even rethinking the maintainer structure), I don't actually hate Drupal (as those of you who grok sarcasm might have noted).

However, Drupal has been my full-time job for 6 years. In that time, the community (and the software) has grown and changed considerably. It has been an amazing ride. As Dries mentioned to me on the phone a few weeks ago, "once a Drupal guy, always a Drupal guy". This is probably true - I have no intention of leaving the community, but I am ready for some new challenges.

Open Web: One thing people may have noticed is that when I have had the chance to hack on Drupal lately - it tends to involve "open web" or "open standards" implementations (notably, OpenID etc). Many folks have also noticed that my contributions have trailed off lately. When your "after hours" time starts including more things like "sleep" - your after hours projects take a hit.

I'd like to get back to building cool, new stuff. While I certainly get a lot out of teaching people how to make the most of the tools available, I'm passionate about building the next tools (which doesn't exclude Drupal). These are interesting times on the internets, I wanna have my nose in the middle of it.

Now what?

Officially, I will be freelancing (technically have been for a few weeks). I've already got some interesting things lined up that I'm excited to start talking about soon.

Almost exactly one month ago, I made the switch from my old, 2g, jailbroken iPhone to a brand new fully legit android phone: the HTC Hero.

My reasons for the switch were varied - it's a platform I'd like to support, hack on and one I generally find interesting. I've also grown increasingly frustrated with my suite of Apple products and, in general, am looking to "live open" (more on that later).

Treats

There are some things that I absolutely love about the Hero: way more than the iPhone:

• It is an aesthetically pleasing device. This is one thing that has kept me on Apple gear for a long time. I appreciate quality design - particularly in the products I use constantly every day. The Hero is a good looking device and feels good in my hand.
• Multi-tasking. Yeah, this is the big "killer feature" over the iPhone, but it's really handy. I consider my phone primarily a communications device and I can see instantly and easily who is emailing, texting, IM'ing or mentioning me on twitter all without quitting the app I'm currently running.
• Contacts a central. On a contact's record, I can see all phone calls, emails and texts with that person - and even their Facebook status (or birthday - nice touch).
• Really great sync. Now, let me start by saying - I'm a google apps user. That said, all I did was add my gmail account information and instantly I had all mail, contacts and calendar entries seemlessly sync'ed to my phone. Oh, and (unlike "mobile me") there was no additional cost.

Frustrations

This isn't quite the ultimate phone yet. Here are my top gripes:

• No paid apps in the Android Market in Canada. I'm confused as to who is really to blame here - whether it's the big US companies or the Canadian government or a combination of the two, but living in Canada can be a real drag sometimes.
• Lag. It's not a blazingly fast phone and when you add running multiple simultaneous apps, the interface can get laggy after a while. A good "task killer" app on Android seems to be a best friend. (I'm currently using TasKiller, FYI).
• Lots of the apps just aren't as good. Twitter apps are a significant comparison - there just is not a tweetie 2 comparable app. That said, there is a google voice app ;-)
• Version lag. This seems to be particularly bad on my HTC Hero (which currently uses Android 1.5), but in general handset manufacturors seem to be slow to roll out the latest version of android for their handsets. Doing so yourself, requires rooting (how is that an advancement from iPhone?).

Conclusion

Overall, though, I'm happy about the switch. I think the Android future is bright and hopefully I'll have some spare time here and there to hack on some things in support of the platform.

For a long time I've maintained that I hate web applications. It's good for a laugh (in certain circles), but has been mostly true. Web interfaces have (traditionally) been clunky, lack integration with the desktop, don't work offline, and are generally just unpleasant to use.

Lately, I've been re-testing that theory and have surprised myself with the results:

I'm living in the browser.

OK, not entirely. But my currently running applications include: Firefox, Emacs, Terminal, Adium and iTunes (sorry, songbird).

The frequent, attentive readers among you know that I've been tinkering with "Single Site Browsers" lately as part of this experiment - because, if I'm using Firefox for development - I don't want "other stuff" cluttering that. Well, a recent article on lifehacker made me rethink my approach.

The article outlines a way to have "permanent" tabs(i.e. tabs that automatically reload when you restart yoru browser) that only appear as a favicon (thus saving screen real estate). My current lineup looks like this :

That's gmail (personal and work), remember the milk, google voice and google reader.

For the last few weeks, I've been trying out this system and have found little reason to want to switch away from it. There are some properties that appeal to me: my application list is entirely cross-platform (substitute pidgin for adium) and free software. Application management, setup and configuration is minimal and I have to do very little application switching throughout the day. In fact, with my external monitor, I can fit everything on one screen where I can see it.

Ditching a desktop mail reader was obviously the biggest shift. But in the case of gmail, rtm and google reader there are a few things in common that make these "work" for me as desktop replacements: offline mode (thanks to google gears), extensive keyboard shortcuts (better than their desktop equivalents), regular updates / improvments and APIs / methods for extensions.

Here's my current list of Firefox extensions, let me know if I'm missing any great ones:

• 1Password
• Better Gmail 2
• Better GReader
• Evernote Web Clipper - still determined to use evernote effectively
• FaviconizeTab
• Firebug (always)
• Gmail S/MIME
• Google Gears - offline goodness
• Greasemonkey
• PermaTabs Mod
• Remember The Milk for Gmail - to help solve the problem of my todo list not getting enough 'focus'

How much of your life do you spend living in your browser?

This past weekend, I had the privilege of being one of the chosen attendees for Social Web FooCamp. Needless to say, I was flattered and had an amazing time (thanks again, @daveman692 and @davemorin ) . One thing, however, became very apparent: the conversation, currently, is being dominated by the 'big players' (Google, Yahoo, Facebook and Myspace predominantly). In several discussions I found myself increasingly dropping the phrase:

... on the rest of the web

the big guys

First off, this is not a critique of the Google's and Facebook's of the internet. They are incredibly valuable to the growth of the openweb. The fact that Google, Yahoo and Myspace all three have various OpenID and OAuth initiatives in the wild and are actively pursuing additional ways to open their data is awesome (and Facebook wants to get there). It helps raise awareness and bring (slash confirm) "legitimacy".

The big guys also have resources. They can attend the conferences (and camps!) and have dedicated resources to write the standards, participate in the discussions and help shape the future.

However, they are only part of the discussion.

perspective

The issues the major providers face are different from the rest. They have a few sites with large numbers of users (hundreds of millions). Out here on the rest of the web, we have millions of websites, each with a "small" number of users (hundreds or thousands). We all understand the necessity for open data, identity, standards and protocols, but our reasoning tends to be slightly different.

The big guys recognize the benefit of exposing their data and most are providing OpenID and various levels of OAuth. How many are consuming it?

Sure, the big players want to be the primary authority for your identity and your information. In some cases, it is their business. But, rather than ranting against 'the man', I ask: have we - the rest of the web - given them a compelling reason to yet?

open source platforms for the open web

It's one thing for a major site (with hundreds of millions of users) to act like a silo, but on the rest of the web it amounts to isolation.

Those of us working on open source web platforms have an enormous potential for influence here. Implementing the various open standards "from scratch", while possible, is not realistic or even necessary. Increasingly, individuals have Wordpress blogs or perhaps their company, organization or club has a Drupal site. Web developers are increasingly turning to these platforms, or development frameworks such as Rails and Django. These platforms all have a real opportunity to bake in implementations of these open standards. The DiSo project offers a central place for co-ordination around these efforts.

We have data - gobs of it. We also, collectively, have the users and, in most cases, have more authoritative information about them (we know ourselves, our employees and our members).

We - the rest of the web - need to join the conversation: attend the events, participate in the mailing lists, and build the code to power the open, social web.