Ultranormal

Category: AOL

  • Adapting to Web Standards: Going to Press!!

    the cover of Adapting to Web Standards - buy two or three copies!

    I just saw the e-mail today that the book I helped write is going to press on Monday!! It’s called Adapting to Web Standards: CSS and Ajax for Big Sites, and I wrote a chapter about AOL.com. It’s available for pre-order now, of course, and would make a great Christmas gift for your favorite web nerd – they might even like two or three copies (really, they might).\
    Writing the book (well, my chapter) was… difficult. I don’t think I’ll write another one any time soon, at least while I have a full-time job. It was a great experience, don’t get me wrong, and Christopher and Victor, our editor, handled all the hard bits. I’d always wanted to write a book, and am grateful that they gave me the opportunity to write a chapter for this one.\
    I can’t wait to hold a copy in my grubby mitts and hear from folks what they think of it (good or bad).

  • Web Standards’ Three Buckets of Pain

    I spent this week at the W3C’s annual technical plenary, which is a week of “discussing” the future of the foundations and future of the web. I spent the first part of the week in the CSS Working Group discussing CSS3 features and CSS2.1 issues. Tuesday evening and Wednesday were spent in the AC meeting and Technical Plenary day (everyone gets together in a big room for panel discussions and lightning talks about standards-related issues – my favorite day of the week). The latter part of the week I spent in the new HTML Working Group talking about a lot of issues I’m not up to speed on because I just joined the working group (but, of course, that didn’t stop me from jumping in).\
    Molly led a panel during Plenary Day called From the Outside, In: Real World Perspectives on the W3C with a handful of designers and developers who aren’t currently involved in the W3C (Aaron, Matthew, Patrick and Stephanie). The panel helped solidify a few things for me and I want to try to explore them in this post. The panel wasn’t bad by any stretch. I think it was brave for them to come into the “lion’s den” and give the W3C their perspectives. But, I felt that the way the panel was presented left people in the audience confused about the overall message, and exposes a huge gap between the W3C’s understanding of “web standards” and the web development world’s definition.\
    Before I get any further, I need to explain where I stand here. I have a foot planted firmly in both worlds. I’ve been building web applications for almost a decade and have been a fan of standards-based development since late 2001 when my blog validated as XHTML 1.0 Transitional. I’ve been a member of the CSS Working Group for about four years as well.\
    The complaints about web standards are varied and many, and the panel made it feel like they all fell squarely at the feet of the W3C. But, that’s just not the case. I think a lot of the problem comes from our (being the web development world) definition of “web standards” being almost completely different from the definition understood inside the W3C. To web developers the world over, “web standards” means: “What I have to do to get my page to look right in all the modern browsers.” The W3C’s definition is “the underlying specifications that implementors (in our case, web browsers) use”. See, the standards aren’t written for, or by, web developers. In the case of HTML and CSS, they’re written for and by the people who create web browsers – which is why they’re so hard for the rest of us to understand. The vocabulary is different. The requirements are different. There is a whole world of pain in store for the brave soul who wants to write a web browser – and it’s a uniquely different world of pain from someone (you and me) who wants to apply those standards to build a web page that will render in one of those web browsers.\
    For the rest of this blog post, anyone building a web browser is implementing the standards, and anyone trying to build a web application is applying the standards. People building web browsers have to implement parsers, renderers, conformance checks, error handling and all sorts of other nasty things to get a browser to function. People building web applications have to take the standards and apply them through an implementation (in our case, a browser). We’re not writing the parser, we’re writing the thing that gets parsed.\
    And there are our three buckets of pain:

    1. The Specifications
    2. The Implementations
    3. The Applications\
      h4. The Problems With The Specifications\
      The major problems I hear about the W3C and its processes are:
    4. It takes too long.
    5. I don’t know what’s going on or when we’re going to see the standards come out.
    6. Spec X is missing this, this and this!
    7. Developers and designers have no voice in the standards at all!\
      One, two and four are, or were, true. Number three is only half true most of the time. Every time I ask developers or designers I know about what’s missing from CSS, I always hear “I want multiple backgrounds and a real layout model. Oh, and border images!” Two of those are already implemented in Safari, and I’ll bet you Firefox will have them done shortly. They’re all in CSS3 somewhere.\
      Web developers and designers have more of a voice on the CSS Working Group than ever. There are currently three designers in the working group (two from AOL and one invited expert). The group is also working with the new CSS11 group, and is actively gathering feedback. The new HTML Working Group has several members who are web developers and over four hundred invited experts (who can’t all be building browsers).\
      The W3C is working very hard at opening up. It’s not there, and they’ll stumble, but the attempt is being made.\
      h4. The Problems With Implementations
    8. Microsoft took a vacation. IE6 has been out (and broken) for a very long time. We got complacent in our hacks and nonsense to work around its “quirks” and now those bad habits and hacks are getting stale.
    9. They don’t move fast enough! See number one. We’re tired of waiting, but laying the blame on the CSS Working Group instead of Microsoft. If Microsoft had been actively engaged in the Working Group this whole time, we’d be a lot farther along. It’s very hard to get to interoperability when the market leader is working on other things.
    10. They have bugs. Every piece of software ever written has bugs. Thankfully, bugs get fixed in the other browsers fairly quickly. Unfortunately, IE is now on a 15-20 month release cycle, which means we have a while to wait until we see things we need like display: table and probably 30-45 months until we can hope to see advanced layout or the grid implemented.\
      h4. The Problems With Applications\
      (this is going to be painful… just hold on – it’ll be over soon)\
      Our biggest problem as web developers and designers is the misunderstanding I pointed out at the beginning. We need to understand the three buckets of pain and what we can expect out of each one. There’s no reason to rush standards out if no one’s going to implement them. There’s no reason for us to try to use them until they’ve been implemented.\
      We have to admit that we made a fundamental mistake in how we advocated building things with “web standards”. As someone who’s done training for the last five years, this is as much my fault as anyone’s. We taught to the implementations. We never taught the distinctions between the specification and the implementation. We never taught that we were teaching an application of the standard and not the standard itself.\
      The hacks became the standard and not the exception. We taught without understanding the long term implications of teaching hack management instead of teaching the specification and the application of it separately.\
      h4. How do we move forward?\
      We need more developers and designers plugged into both worlds. To work on the specifications themselves, or even read and give feedback on them, you have to abandon any hope that this will be useful to you in your development world for three to five years. Once you do that (it took me two years to get that through my head), you’ll be much less frustrated, and might actually be helpful. To a degree, you also have to abandon your notions of how you do things today. When thinking about layout, you have to give up thinking that “float” is the best way to do it (because, please, it’s just not).\
      We need to reboot our perceptions of web development and start thinking towards the future. It’s a new world, and getting newer every day. Our best practices have to evolve – our disciplines have to evolve. We need to think about a world without IE6. It’s going to happen. We need to come up with better ways of building web applications. We need to come up with better ways of teaching the value of web standards. We need to do a better job of educating designers and developers about the consequences of building web applications. We told them all the good things that would happen when they did it our way, but did we tell them that hacks go away? Did we tell them that browsers evolve and that hack they spent all that time on to get things to line up in IE6 will go away some day?\
      I don’t think I covered everything I wanted to say. There are a lot of things swirling around in my head right now. I had my mind blown last week by this realization and it will probably take more thinking about it before it really crystalizes and I can really explain what I’m feeling. But, right now, this is it, and that’s as good as I’ve got: It feels like I’ve spent the last 7 years living a lie, but the truth is so much more interesting and complex than the lie ever was. It feels like a stronger foundation, but wider and darker in the corners, than the one I’ve been standing on.

  • That’s the Spirit

    This week has been difficult, to put it mildly. As you may have seen in the tech news (and hell, maybe the regular news too), AOL laid off a bunch of my friends this week. I’m still employed, but it’s never easy to see the company I’ve been a part of for twelve years shrink. I’m not sure what’s going to happen, but for now, I’m not giving up. I twittered last night that fighting is much more fun than surrender, and it’s true. Between the web standards stuff Kimberly and I started four years ago, to working on the stuff that’s come after it (the Cluetrain, Rails, etc), I’ve been fighting to “save” AOL for years. I’m not ready to give up on that investment yet.\
    This week has been all about mourning and trying to make sense of what’s left. I wasn’t going to write anything at all about the layoffs here, but I saw something today that was so unbelievably awesome, and says so much about the people who make up the company, that I have to share it. Upper management may change every year or so, but the people who work here are what’s always made AOL work and made it a fun place to work. Check out this video (the password is aollover and I found it over on Silicon Alley Insider):

    L’amour a la francaise from pyc on Vimeo.\
    I’ve been to that office. It was many years ago, but they’re great people, just like the great people in Dulles, Dublin, Mountain View, Columbus, Tucson, Bangalore and everywhere else we have offices (those are the ones I’ve been to anyway). I’m hoping that when it’s my time to leave, I can show as much class and heart as the folks in the Paris office.

  • The Internet Fast

    I’ve been stressed out a lot lately… and pretty consistently for the last two years. It finally came to a head this week, and I decided I needed a break from everything. So, I decided that yesterday through Saturday, I would try to live completely without the internet: no blackberry, no laptop, no wi-fi, no nothin’. Since it’s only Friday afternoon, you can see – it didn’t go so well.\
    I’ve worked for AOL for over twelve years. In that time, I’ve only been completely offline for more than twenty-four hours twice: first when a bunch of friends and I went to Carlsbad Caverns and none of us had laptops yet (this was 1998), and in 1999 when Jen and I got married and went on a three day cruise. That’s over eight years of pretty much constant connection to e-mail, IM, and everything else.\
    Back to the break… in the beginning of my internet life (1995), it was just e-mail, and not a lot of it. I worked with a relatively small number of people, I was relatively isolated within the company, and wasn’t involved in anything outside of work that would produce much e-mail. Then, came the buddy list and instant messaging. OK, two forms of interruption, but pretty much exclusively used for work and at work. Fast forward 12 years, and now here’s what’s built up in the almost thirty-six hours I was able to stay away until the DT’s got me and I had to check:

    • over 270 e-mails
    • over 2,100 unread items in my feed reader (from 581 feeds – recently pruned down from 680 – and I just marked them all read… didn’t even read ’em – it you blogged something you really need me to read, send me e-mail)
    • untold messages on twitter (I haven’t even checked… thankfully, I can ignore all of them and I don’t think anyone’s feelings will be hurt)
    • 45 Facebook notifications (also ignored, mostly because I don’t like Facebook)\
      I checked recently and I receive, on average, 21 instant messages an hour (that’s almost 200 during the course of my regular 9 hour work day).\
      If you figure that out over twenty-four hours and consider the last day and a half “average” (it feels like the normal flow), I handle over 1,700 distinct pieces of communication and information a day, and still manage to do my real job, which is not to just read e-mail, respond to IM’s and read feeds. This pace has only increased in the last five years, and doesn’t show any sign of slowing. It’s only getting worse.\
      I’m not sure what the point of this was, other than to document for myself how bad my information overload is and trying to explain to myself that it’s OK that I was overwhelmed. Dealing with this ever-increasing torrent of data every day for over a decade – it’s OK to take a day off. It’s OK to let people answer their own questions, let the world keep spinning while I take a day to close my eyes and read a book (I’ve been reading Pilgrim at Tinker Creek by Annie Dillard to try to cleanse my system from all the technical books I’ve been reading in my spare time… the most beautiful English prose I’ve read in a long time – a modern Walden).\
      I have another blackout day coming. Monday, I’m heading to London for the Future of Web Apps conference. I’m looking forward to the speakers, but, I’m really looking forward to the eight hours of uninterrupted (well, mostly) reading time on the plane where there’s no way for me to check my mail.

  • Art in Social Networking Video

    After our Art in Social Networks session at Mashup Camp, someone asked if Greg and I to recap the session. There is a lot more info on the wiki, and Myk O’Leary recorded the whole thing and posted it as well if you’re interested.

  • circaVie

    It looks like we’re on to something here… first, we launched ficlets. Now, Dave McVicar and crew have launched circaVie. It’s a cool site for building timelines of pretty much anything. There was a bit of overlap in the ficlets and circaVie crew. Jason Garber did most of the markup before he scampered off to join his startup. Jenna Marino, who designed the gorgeous ficlets logo, did UI design for circaVie. Ari Kushimoto, who did a lot of ficlets’ UI, was circaVie’s art director.\
    I love seeing things launch, especially stuff as beautiful as circaVie. It’s an amazing piece of design and engineering. The site is gorgeous (I would say “lickable”, but that’s gotten me in trouble before – not doing it, just saying it, so I’m not saying it). The Flash stuff feels perfectly integrated and the interaction is really smooth. Jayna Wallace was the visual designer and did an amazing job. Corey Lucier did the flash work. Kelly Gifford jumped in and took over the markup when Jason left. Plus, it’s all on Rails!\
    Update: AUGH! Dan reminded me in the comments that I left him out, and I certainly shouldn’t have. Dan Bradley is the operations guy for both ficlets and circaVie, and I’ve worked with him for at least the last five years (probably closer to seven), and he’s one of the best there is. He helped a ton getting ficlets out the door, and I’m sure he’s done the same for circaVie.\
    You really should go check it out. The team worked really hard on it, and it shows.\
    See also: Kelly’s blog post, Mashable and Somewhat Frank.

  • Portable Social Networks at Mashup Camp

    I’m doing a presentation today at Mashup University that I’ve titled Tapping the Portable Social Network that’s a code tour of how to create a social network that uses existing social connections and public data to make the sign up process for web sites easier. Of course, this whole idea came from Jeremy Keith.\
    It’s a very simple Rails app (that you can download) that only deals with the login/signup process using both OpenID and AOL’s OpenAuth.\
    Here are the basics…\
    If you log in with OpenID, it:

    1. grabs the identity URL, and looks for some microformats
    2. looks for an hcard and pre-fllls the profile
    3. looks for XFN-encoded links and searches the site for existing users with that homepage and gives you the option to add them as contacts when you sign up.\
      If you log in with OpenAuth, it:
    4. pre-fills your profile with URLs and data we think we know based on your screen name.
    5. grabs your buddy list and looks for folks who logged in with those screennames on the site and gives you the option to add them as contacts.\
      It’s dead simple and poorly documented, but works well so far, and I think the flow makes sense and has possibilities. You’re welcome to take it, the concept, the code, and do whatever you want with it.\
      The next step is to see what other open reliable sources of social data are out there that would make sense to look for during the sign up process.\
      UPDATE: Read the README file! There are several things you need to change in both the configuration, and one line in profile.js. The README documents all of the required changes and where to find them.

  • This Week’s Ficlets

    I’ve been writing ficlets at night after work as a way to unwind and do something creative outside of writing code. It’s been fun! I’ve been trying to write sequels to other peoples’ stories as an exercise in trying other styles, genres and voices. I think I’d call the results mixed, but fun.\
    Here are this week’s:

    • The Devil in a Shop Window – I seem to do tragedy pretty well. This is a sequel to a story about alchoholism and hitting rock bottom. The original provided a perfect setup.
    • Shokran Gazillan – I had to do research for this one (looking up “thank you” in Arabic). It’s a sequel to a story about a soldier in Iraq on patrol stumbling on a wounded Iraqi child and his brother.
    • Basil, Rock God – A sequel to a hilarious story about an accountant who wakes up in the body of a rock star. Lots of questions to answer, but all I wanted to write about were leather pants and his stupid non-rock star name.
    • Keeping the Peace? What Peace? – I re-read Shokran Gazillan and had to write a sequel to figure out what happened next.
    • God’s Fist – A sequel to a great Deep Impact~~style story about an impending comet impact. Reminded me a lot of the first ficlet (oddly enough called The End) (which has spawned a surprising number of sequels~~ it’s actually got a bunch of threads coming off of it!).\
      Jen came downstairs earlier and asked me if I was working (before I started writing, I was checking on stats, checking for reported stories, and wander). I gave her a blank look… was I? She laughed at me and told me it was OK if I was working. I shook my head and told her I was playing with my “toys”.

  • Watch Jeremy Schaap Talk About Nerds

    AOL’s sponsoring TopCoder again this year, and one part of the promotional materials stood out:\
    bq. Over the course of the three hour webcast hosted by ESPN’s Jeremy Schaap, viewers will be able to watch the high stakes software competition unfold through live views of the arena, entertaining coder profiles, and interviews with contestants – all culminating with in-depth coverage of the final results.\
    Now, of ESPN’s reporters, Mr. Schaap is #2 when it comes to possible closet nerd status* (their awesome NFL guy, John Clayton, is #1), but it just cracks me up that we’ll have play by play for a coding event. It’s worth checking out for that alone!\
    If you want to play along, the coverage starts at 4 EST today over on the AOL Developer Network. They’ve even put together a preview video.\
    *I’m saying this as a full on nerd. There’s no shame in being a nerd. Flaunt it, Schaap, flaunt it!

  • My New Standards Role

    My New Standards Role

    It’s finally official and I can talk about it… so I am! My pal, Arun, who has served as AOL’s representative on the W3C’s Advisory Committee for the past three years, has been elected to the W3C’s Advisory Board. That’s a huge honor, and very cool, both for Arun and for AOL. That means he’s got his hands full – what with his membership in two working groups and his spot on the Advisory Board (plus his day job). So, I’m going to take his spot on the Advisory Committee! It’s a huge honor to represent AOL at the W3C and I’ve got my work cut out for me. AOL’s participation in the W3C while Arun was AC has blossomed, but there’s more work to do. We need more folks to participate, and participate in a meaningful and consistent manner (something I’ve not been able to do in my time in the CSS Working Group, unfortunately). It’s as much a management problem as it is a technical one, to give people the time to contribute beyond the travel (and a time management problem – we’ve got to be willing to carve out the time).

    There’s lots to do, lots of folks to recruit to “the cause”… and I have to find some way to abuse my new power!!

    (there’s no real power, just a lot more e-mail, apparently)

    For now, I’m going to try to remain a member of the CSS Working Group, but I’ll probably need to drop it and concentrate on my duties on the Advisory Committee. Thankfully, we’ve got Jason and Justin, two super-talented designers, to take my place!