Pages

February 28, 2006

Content engineering

You know what's nice about the Internet, as an end user?

You don't have to install the Web.
You don't have to upgrade a webpage.
You don't have to download a whole website before you can begin perusing it.

Some nice examples of actual applications as content:
http://www.gapminder.org/ (Flash)
http://babynamewizard.com/namevoyager/lnv0105.html (Java)
http://www.dhteumeuleu.com/ (DHTML)**

These are a little data-viz centric, I realize, but hilights (for me) the difference between the old world of content and the new (hint: Its participatory :P)

**OK, this one's just demo-ware, but it shows that just DHTML fun can be had.
To use it, click a category, then select a demo in the list below that, and then click ON the demo picture itself to activate it.

February 26, 2006

Javascript Applications, pt 1

Updated: Continued in Part 2.

Languages (and language studies) are an interesting phenomenon. As we know from anthropology (and middle school social studies), Eskimoes have 20 different words for various kinds of "snow", whereas we have just the one: "snow".

Now, it turns out this is just one more in a long line of urban myths that we've repeated into "truthiness" - and that's also interesting (but a whole 'nother discussion).

We look at language as deeply revealing reflections of underlying culture and structure. And while I don't deny the power that language has and the values that it can imply, I don't believe that it fundamentally enables new capabilities for a society. Is there a language that lacks poetry? Or laws? Or stories? Or religion? And I'm not sure a particular language, in and of itself, has any particular evolutionary advantage - though clearly a particular language's economy of communication is likely a reflection of a culture's evolutionary challenges.

For computer languages, this seems even more apparent. I mean, its pretty much the same CPU underneath, so the language is just a question of vanity and preference, no? It really doesn't matter what language you use, so long as you use it well?

Turns out, not so much
.

Although I think there is a fundamental provability to the notion that good programming is language invariant, the grammar and semantics of a particular language can be measured along a number of axes:


My point here is that language features are not about CAPABILITY: you can (literally) do MORE in Assembly than any other language (although, you know what they say: you can't spell "Assembly" without "Ass"). But languages developed - some evolved, some were designed (intelligently and otherwise) - because there was a need to enable significantly greater complexity and abstraction on top of vastly increasing linear computing power.

Bottom Line? The abstractions various languages provide ultimately matter because they enable significant flexibility, at the cost of some performance. Its all just a question of the value of the tradeoffs.

Pretty long way to go to say that I think while Javascript is great, it also sucks.

I'll explore what features have been valuable and where we've suffered using it to build
desktop applications in my next posts on this topic - along with some specific recommendations (for developers USING Javascript, as well as suggestions for the language itself).

As I've
mentioned before, I think we're among the bold few attempting to use Javascript for Programming in the Large for desktop applications, at scale. Though AJAX is all the rage (*cough* DHTML), the discussions tend to center around "Bitless applications" - stuff in the browser.

A lot of the problems are essentially of the same type (but exaggerated for desktop apps), so I think most of the discussion applies to both, but, obviously, there are some interesting differences as well.

February 24, 2006

Credit where credit's due

This is a follow-up to my previous post.

I think a lot of us at the bigger software companies are here for more or less the same reason: the opportunity to impact hundreds of thousands, if not millions, if not tens of millions (and more) users. It feels great to feel like your work matters - and to be
recognized for that.

Heck, for that matter, I think many folks at smaller tech companies feel the same way (though there, its often more about potential than realization).

That impact might even be life changing; or inspirational; or there might be unintended happy consequences: you connect people, enable them, and/or empower life defining moments. At enough scale, you can start do all of those things, and it can be rewarding.

But there's a big difference between doing good, either as a side effect or with ancillary (financial or corporate) benefits, and intending to do good, for its own sake. There's a difference of will that I think is morally significant.

So in that spirit, I have to say: I'm proud to be a part of an industry that is starting to
actively accept the social authority and responsibility that comes with great power: to intend good. I try in little ways - and we do a LOT of community and charity outreach at AOL, but I am humbled by the ambition of vision I see and the opportunity for impact it implies.

(BTW, if you don't know the man they appointed to run
google.org, Larry Brilliant- I didn't - pretty seriously cool.)

February 22, 2006

About... credits

Updated: David Besbris makes a point that is more or less at the heart of why I think this matters: Software is a players' game.

I was recently reminded: one of the nice minor things I feel quite proud of helping accomplish during my tenure here is the (re)instatement of credits in our "About..." boxes at AOL for our desktop applications.

Most of the things that that my group has done has really been my group: I might have helped make the room, but others better than I filled the space. And the ideas and desire had been here long before I started.


This one was I feel I contributed to more directly, though :)

Its important that the people building the software feel connected to it, and pride of ownership is a key part of that. I'm even more pleased that software engineering come first in that list - that's on purpose.

Other folks, like Product teams, Business owners, Marketing, etc. have other outlets for this pride of ownership - whether its because of press interviews, org structures, or simply because they're the ones delivering the updates and plans in executive reviews and public forums inside and outside the company.

But programmers? We make the product.

I realize its very, very trite, but its also very, very true: The intellectual capital at software companies is in the people, not the code.


Not like a big initiative or anything, but I'd like to find some way to do this for "bitless" applications (online only) in a "standarized" way as well - its not about being splashy or territorial, just giving credit where its due.

February 21, 2006

Present in the Industry

My woman - that is, my wife, who it turns out DOES read my blog, and would henceforth liked to be referred to as "my woman" (she finds "my wife" to be too 1950's) - anyway, "my woman" has been known to give me a fair amount of grief for not being "Present". She says I'm often thinking about other things when I'm supposed to spending quality family time with, well, my family. So I've really been working on being "Present" (though working on this post might be considered evidence to the contrary :)).

In a similar way, one of my specific goals here at AOL is to help us be more "Present in the Industry". It bugs me a little (read: a LOT) that when people talk and think about Internet companies and the behaviour transformations driven by technology, AOL often doesn't even make the top 10 (Google, Yahoo, Amazon, E-Bay, Microsoft, Apple, Skype, MySpace ... yada yada yada). Or the articles tend to be stand-alone "What ever happened to...?" style COMPANY articles - they're not enough about our products, technologies, and services in a real competitve business context (side-by-side reviews, recommendations, etc.) , i.e. the relevance of our efforts in the industry.

Now (historically), that's not THEIR fault, its ours.

The
good news is I think this is changing. We're STARTING to show up on the same page with other relevant, competitive Internet technologies (which means we're STARTING to matter again), in small ways, though its still with some surprise ("Maybe its a fluke?", they think; "If only it didn't say 'AOL'", they write).

We've had a lot of internal
reformation and disentanglement that we needed to achieve here over the last year/year-and-a-half - both technically and organizationally. And though we are FAR from done, I think we're indeed over the hump - these emerging AOL technology and employee blogs are but one, small, visible sign of this.

Our progress in this regard, I expect, is going to be accelerating much more visibly, in some
substantial ways, over the course of the next year. As these things become more public, I'll be expanding my discussion here to cover our increasing efforts across our whole technology base to be MUCH more present and transparent, "in sych" if you will (sorry - inside joke :)), with the Internet community at large - with products, services, and, yes, technology.

If AOL is going to become relevant again, if we're going to be "Present in the Industry", we're going to have to erase the boundaries between AOL and the Internet, and between AOL and your computer . We need to become an increasing part in the clickstream and thoughtstream of an increasingly connected world - in the browser, WITH the browser, and beyond the browser.


And I believe that this is as much a cultural transformation for us as it is a technological one.

Our karmic niche is pretty simple (no, not
this one, wiseguy. :P): We democratize the Internet - making powerful things accessible. Too often, especially during the heady boom/merger days, I think we realize AOL took the "So easy to use no wonder its #1" mantra a little too literally. Understood the wrong way, it can became about being "dumbed down" instead of "empowered".

February 19, 2006

Legal Security: OCP and Apple's Intel Macs

John Robinson continues to expand his discussions on the runtime layer underlying our new desktop software architecture, the OCP. His post is here, with some background discussion here.

There's some novel concepts around services and process groups John
covers, and a few unique details he skims over without real comment, but I wanted to point out one specific, um... interesting thing he mentions only in passing - the OCP Haiku that you (developer-"you", not end-user-"you") must submit (in code) before you can activate and consume services:

Writing Code
The Dawn Sun Breaks
I am at Peace

-
The OCP “Haiku”© AOL 2003-2006

Almost exactly like the
poem that Apple embedded in the software/hardware interface of OS X for their Intel Macs, this isn't a cute wink to hackers or a nudge to anyone's conscience: its actually a platform "security" feature. The idea is not to prevent hackers, per se, but to try and cloak one's technology with as many legal protections as possible to prevent "white hats" from absconding with your IP without recourse. In the OCP design, we attempt to engender the protection of patent, contract, DMCA and copyright law - our Haiku being about the latter two, in particular, of course.

An original poem is the smallest legal copyrightable work - or I should, a poem is a copyrightable work, of which a Haiku is the shortest legally recognized form (or so I'm told). Incidentally,
John was the author of our OCP Haiku - we held an internal contest amongst our client developers, and his was selected as most poetic.

It will be interesting to see how this
turns out for Apple - as far as I know, these types of protections have been in the theoretical category (legally speaking), though they've been extended and applied in the real world in a number of novel ways (including ours) for a few years now.