Monthly Archives: June 2010

WWDC 2010 Wrap-up

I’m leaving San Francisco, and Apple’s WWDC, this year more introspective than inspired. The conference puts us under NDA, so while there was some new stuff shown and talked about there, I can’t pass it all along. Not yet anyway, there should be some interesting new stuff to talk about once iOS 4.0 is out and in the wild.

It’s no secret that most of the conference focused on the iPhone and iPad – what they’re now calling “iOS” (and yeah, I thought “Hey, doesn’t Cisco own that brand name…” when I first heard it). The desktop/laptop Mac OS X didn’t get much play time, the iOS operating system instead getting the red carpet treatment.

The engineers at Apple have managed to build, update, and ship an entire OS for specific platforms once a year for the past 3-4 years. I’ve got imagine that they’re nearly, if not completely, mentally bust at this point. I’m not at all surprised that “iOS 4″ won’t be out until Fall for the iPad – I suspect they’ll call it iOS 4.1 or 4.2. Apple’s not growing like mad (at least that I can tell), which means to me that they have been and continue to push at a fevered pitched for the accomplishments they’re making. I hope they don’t push so hard they fry their best and brightest that make up the core of the culture that’s doing all this impressive lifting.

The “other focus” of the conference was around new developer tools – Xcode 4 (developer preview) is quite a bit of engineering and accomplishment. To me it’s centrally a fulfillment of an idea that Chris Lattner presented and posed for possible futures in an LLVM session two years ago. It is more than that, and I’d love to wax a bit more enthusiastic about it, but I’m afraid that runs into NDA covered territory, so I’ll stop here on that topic. I did come away from the conference having submitted more enhancement requests than ever before around that tool chain.

Dr. Michael Johnson (@drwave) gave a talk in the middle of the conference, impressive in display and content, and really talking to the “why” and “how” of making tools. The message I took away this year from his talk was akin to an artist extolling “know your medium”. He didn’t outline the pros/cons of each medium that he works in per se, but just expressed what he could do in each and why knowing that medium was important. I’m still reflecting this year’s talk off the meme that he was touting a year or more ago (and was reflected a bit in this year’s talk too): “using tools to remove the tension in the room”. I guess it was two years ago at WWDC, we talked a bit. He related a viewpoint that “tools shift power” and was being very mindful of wanting to shift it in a way that was ultimately positive, not negative. Being a bit of a tools guy myself, I find myself reflecting on that quite a bit. The real bitch is that it’s often hard to predict which way the “right way” is between organizational politics and getting our jobs done.

For all the cool and amazing stuff that I saw at WWDC, I’m finding that I’m not walking away from this one inspired, scheming, and planning for something new, cool, etc. Oh, there’s the idea for the iPhone or iPad client application to this or that, but really I find myself instead thinking about my day job.

This week has given me some much needed time to step back and away from the office. I deleted my mail accounts from my iPad and iPhone to make sure I wasn’t even tempted to check them (those red badges can be like a red flag to a bull when you’re a somewhat compulsive person). What are we really focusing on and what difference is it going to make? How do we push or pull the whole organization forward to make it better? I have ideas. Some “maybe 60-70% right” ideas but no definitive “I’m 100% sure of it” answers right now.

Rites of Passage

I saw on the news last night a story about a girl (Abby Sunderland) being rescued while on a solo around-the-world sailing trip. She was in the Indian Ocean, and the rough seas had taken their toll on her boat, demasting her and leaving her drifting. She’d been on a sat-call apparently when it happened, and the sat call (which used the mast as an antenna) was abrubtly cut off. Her emergency beacon’s went off and Search and Rescue out of Australia came roaring out, found her and verified that she was OK and stable (the boat wasn’t taking water) – they should be picking her up today, if they haven’t already.

Abby is 16, and was going for a record: youngest solo around the world. Pretty damned impressive.

At the article in the Seattle PI online, the first comment was made by someone calling themselves “Bobert”. He wrote:

Her dad’s a moron, no need for a 16 year old to sail solo around the world.

I don’t know who this person is, but whomever they are – they symbolize something that is very, very wrong with our society today. Preserve and protect at all costs. What the fuck have we come to? Our rites of passage are down to “driving”, “graduating from high school”, “getting laid for the first time”, and sometimes “graduating college”. What happened to Thomas Jefferson’s american ideals – where the hell did we loose them? Maybe what passes for mainline culture thinks a rite of passage is a barbaric, untidy thing. It’s “dangerous”, and not for those who haven’t “proven themselves responsible”. They might get hurt.

How the hell do you prove you can be responsible in this day and age? By looking down, fitting in, not making waves, and getting by? We need to be looking up and out, trying things, and reaching out for our limits. We need to think, plan, and move ourselves forward, not just follow along.

I don’t know about being in the Indian Ocean during the winter months down there, but to my mind Abby was taking a rite of passage. Also trying to get the youngest-solo-around-the-world record is neat, but to me somewhat irrelevant. She was going out and doing something that I’m sure has touched her in some significant ways, and none of the externally visible.

One of the best things I did around College was go one a four-month walk-about in Europe. By myself. Right after college, I got a backpack and my parents got me the tickets and a Eurail pass. I was off. I think that was my most significant rite of passage. Being by myself for months, in countries where I didn’t even speak the language, teaches you something about yourself.

So to the Bobert’s out there – wake up and fucking smell the coffee. We are not going to make a difference in the world by being sheep. Going on a rite of passage, by whatever you want to call it, should be praised for the effort, not belittled.

WWDC 2010

Ticketing system replaced and launched, I’m ready for a decompress. There’s pretty much no better place to do that, in my mind, than at WWDC in San Francisco this coming week.

I used to send myself every other year. Strangely, I’ve been attending for over 10 years now. Seems odd that it’s been so long. It’s been wild watching the changes in the conference over the years. This year is no different. There’s hardly any “just” MacOS X sessions now – iPhone and iPad (not surprisingly) crowd out the whole schedule. The time to selling out the conference is shorter this year than before, and I rather expect the crowds to be as insane as ever. Fortunately, many of my friends from Seattle Xcoders will be there – even if they love taking digs at each other over sax interface xml parsing code and “unnatural love”.

Best of all, the really big project weighing on my mind for the past month is out – I can go play, hack, drink, laugh with my friends, and not worry about deadlines for a while.

Post launch

Objectively and now a few days past the launch, it went well. During the time it was happening? Didn’t feel like that so much until Thursday afternoon and Friday.

We ran into a failure during our final validation runs, and it opened up a potentially nasty can of demon worms. The basic functionality of a ticketing system isn’t usually the problem – it’s all the tendrils and automation into other components in the organization that are such a pain. In this case, the system that took in email and created tickets from that showed a rather nasty flaw at the last minute. Nasty because it was so damned inconsistent.

Even though we opened a “Pri 1″ bug with our vendor, they didn’t seem capable of getting a developer to look at the code and tell us what the hell was going on. After about 6 hours on the phone with various support technicians, I was personally convinced that they solved the “how to do this problem” in perhaps the most complex and ass-backwards way possible. It spurred us hard to go find all the key elements that were sending in email (quite a trick) to create tickets – which we did, and found that all but one of them were working for a launch. So we did what we probably should have done and created our own mail processor – python and the email library makes that brutally simple, and from there we just push in tickets into the system through their web services (ugh – SOAP) interface. I’ve become reasonably competent at using python suds now as well – it’s a pretty reasonable SOAP library for the basics. It is maybe 3-4 days work all told to get that all in place, extend our REST API interface that we’ve wrapped around their crappy SOAP one, and make sure it passes a battery of half-way sane tests. We’re still finishing that work up now, but it should be all out and rolling early next week.

So we pulled back from launching on Tuesday and ended up launched on Thursday morning. The best part of this launch was getting the deluge of complaints Friday about something not being bolded, the default sort order being wrong for this or that person, and the general user experience model that the application provides (it really likes to use pop-up windows). It absolutely made my day, because that’s all stuff that can be fixed pretty easily – and nothing in it was a major “I can’t do my job now…” kind of thing. My team successfully did an engine transplant on the organization while we kept on running down the road. I expect we’ll falter and hesitate a few days from this – it’s pretty deeply embedded in the org – but we pulled it off.

I think the thing that stands out most profoundly was a tidbit in the kudo’s/Thank you note that my VP sent out about the project:

I talked to the lead Program Manager from ENTERPRISE-VENDOR yesterday about our implementation and he told me that he hadn’t seen a better one in the past 4 years.  Apparently we did in 3 months what most companies take a full year to do!

Not too damn shabby.