
Two excellent conferences coming up in the next few days that I strongly encourage you to attend.
First, this weekend, the very first BarCampSeattle takes place at Adobe's offices in Seattle. The intro session starts at 10am Saturday (tomorrow) so be sure to get there early beforehand to get your badge etc. Watch Robert Scoble interview lead BarCampSeattle planner Tara Brown about what's in store for those that join us for BarCampSeattle.
Join us for the informal BarCampSeattle pre-party tonight: Thingamajiggr and follow barcampseattle on twitter for updates.
Second, next Monday through Wednesday is Supernova 2008 in San Francisco. Organizer Kevin Werbach has done a great job of bringing together an incredible set of speakers and participants and continuously evolving Supernova's format.
Kevin asked me to help out this year with organizing and chairing the Open Flow track which takes place on Tuesday the 17th (I've been organizing it on a wiki page of course where you can view the latest updates and details. We've got good contrasting discussions planned on the topics of what do large companies mean by "open" since they seem to act so differently, what are the realities of "open" as a business model, what is the independent developer community doing to push "open" forward, and finally a session to throw all those viewpoints together and see what happens.
Just this past Tuesday we held a teleconference preview on Open Flow. You can download the MP3 (109 minutes) and view the log of the simultaneous IRC chat as well.
Follow supernova2008 on twitter for updates and hope to see you there!
"Death is a natural part of life. ... Mourn them do not, miss them do not." — Yoda
While a mythical Jedi Master may have achieved a level of inner peace to handle the loss of a close personal friend with such calmness and dignity, the rest of us must simply do the best we can and perhaps cope by sharing. I decided to Twitter not just my experiences the day of Erdal amca's funeral, but also a realtime construction of a series of steps that came to mind (a protocol if you will) for handling such an event. As tweeted:
I leave you with a few positive paths.
May has been a much more personally challenging month than I could have expected. I set out to switch my focus from internal to external and made it less than halfway thru that transition.
It started out with a wonderful spontaneous trip to Seattle, having a great time hanging out with Tara Brown and Ryan McMinn (thanks for hosting!), and a day of last minute meetings with many other Microsoft folks discussing microformats and evolving Communication Protocols for greater efficiency and productivity. Returning for mere hours in San Francisco I managed to repack for New Zealand and go climbing before jetting off to the other side of the international dateline.
The microformats workshops in Wellington and Christchurch went very well (thanks Webstock folks! Natasha, Sue, Mike), and I had a wonderful time in New Zealand exploring streets, cafes, climbing gyms (thanks CJ and Simone!) etc. A week was just enough time to feel familiar with a few things, meet some wonderful people and leave me wanting more.
I hadn't been home for more than a day before having the chance to return the place-to-crash favor to Ryan. A few days later my parents visited with some friends of theirs wherein I played impromptu tour guide and even got them to hike up Lombard street!
The next day a peaceful sunny hike in Muir Woods helped with reflecting and processing many thoughts.
A few days after that Jason DeFillippo successfully introduced Shayla and me to skateboarding. By the end of a couple of hours of practice we could do laps in the parking lot. Neighbor and relatively recent friend Micah helped me fix/tune-up my bicycle so I could put that to use as well. Learning a new physical skill (or refreshing old skills) increases cognitive alertness.
That week my dear friend Micki and I spent a day at the NetSquared conference (an annual source of inspiration for us both), and perhaps more importantly had the chance to catch up on many things during our drive to San Jose and back. That evening we got to meet up with Tara and Sean (near the end of their roadtrip from Seattle to LA) and few more friends to enjoy fake meat dishes at the vegan restaurant appropriately named "Enjoy Vegetarian".
Good conversations with many friends on many topics. As much as I tried to focus externally, I kept finding more and more that challenged me internally. At home I managed to get rid of several boxes of stuff (gave away to friends, set aside for BarCamp, donated) which helped lighten the load. Reducing physical clutter helps to reduce mental clutter.
At the end of the month, Tara stopped by SF for a few days. We celebrated Juliette Melton's birthday with some excellent Rock Band at Trammell's place and more conversations with good friends.
On this last day of May we packed in quite a bit. In another instance of facing something I've found uncomfortable or disliked in the past, with Tara's encouragement I jogged (most of) a mile to Jamba Juice in the Inner Sunset and back. I want to be able to run, at least short distances (a few miles) without difficulty, perhaps even sprint a mile if necessary, and clearly I have some work to do to get there.
We had planned to go to the Union Street Faire. However I finally followed up on a voicemail my father had left me (my sister txted me and told me I should call because "It was important" - always an ominous phrase), and found out that my adopted uncle Erdal amca had just passed away. As much as I tried to hold it together I couldn't. I broke down and was very lucky to have a friend like Tara around to comfort me, give me hugs and tell me it was going to be ok.
Eventually we made it down to Coffee To The People where we intended to just get coffees to go but ran into Eran and his friend Nina who had apparently also done the Seattle to LA roadtrip - 10 years ago - and thus much happy serendipitous conversation took place.
With the clock passing 5 the window had effectively closed to attend the Faire so we decided to be spontaneous. As we hit the road the skies opened up, the clouds cleared away and minutes later we found ourselves in Sausalito where a little walk along the Bay with hot cocoa/tea helped put things in perspective.
Rushing home to change for the Laughing Squid party we took the Presidio exit after crossing the Golden Gate bridge and despite not having the time to do so, stopped by to see Yoda for answers and inspiration. Drove directly to Blowfish Sushi meet up with Tara's friend Matt (another ex-Microsoftie who also worked in the Mountain View campus who I also never met and yet we both knew enough people in common to share tons of stories). Skipped changing and just went directly to the Laughing Squid party a couple of blocks away. The evening ended with an informal escape to a nearby bar with the usual suspects where we didn't stay too late since we both had things to do early the next morning.
This month went by so much faster than I expected. I think I predicted about 50% of what happened, and the other 50%, suffice it to say nearly knocked me off balance and probably would have, had I not had the support of my family and so many good friends (and perhaps an increasingly strong sense of balance from all that rock climbing). I can only hope I can provide my family and friends the same or better support myself.
I learned I had more vulnerabilities than I thought I did, and also learned that I had it in me to face (rather than deny, avoid, or suppress) new and different levels of emotional discomfort and pain, learning lessons, and growing stronger in the process. With rock climbing, often times you have to push yourself thru physical pain or exhaustion in order to make progress, to finish a climb, to develop your technique, get stronger, and gain confidence. It seems this is true in matters of the heart as well.
On the other side of confronting, facing, and understanding pain are new levels of strength, whether physical or emotional. Though self-realization of greater emotional strength and stability is its own reward, even more rewarding is putting such strengthened abilities to use and providing even more open and solid support to your friends, especially those you care deeply about who may need it the most.
Next month I have only one trip planned and two conferences and I think that will be plenty. I'm continuing to push on with focusing more externally but I have a feeling I'll continue to be personally challenged as well. Despite not knowing exactly what form they'll take, after facing May and coming out stronger than I went in, I can truly say I am not afraid.
Bring it on June, I know you will, and I will seek out and face your challenges with open eyes.
I attended the Diggnation party at Mighty tonight. Having driven yet not had dinner, did not partake of the drinks offered. Earlier I had tended to a few appointments and the Data Portability meetup on rel="me" - Chris Saad had invited me to attend and help with Q&A.
A number of things happened over the course of the evening which made me think. Most of them were events occuring in a longer sequence, pieces that helped complete thoughts in progress. I won't go into details but suffice it to say it has inspired a change in focus. Here are some of the topics.
I had most of a blog post written about the etiquette / apparent rules that I'm using for accepting / following / leaving / blocking people on various (semi)real time services like IM, Twitter, Pownce, Dodgeball, Dopplr, and most recently BrightKite - this was going to be my SXSW Tip #2 (and may still be). However, since such rules are always in evolving and changing as new situations occur, I realized that the documentation of such etiquette is much better suited to a wiki. A couple of mini-tips for now: add nice people that you meet in person, drop people if they're mean or noisy (by your judgment).
Such etiquette inevitably touches on the topics of friendship and flirting, two things that I'm still learning lessons about, and as a self-acknowledged late blooming introvert, will undoubtedly continue to do so. However I've learned enough to share, and again, will do so via wiki. Until posted, I'll leave you with the principles of transparency, respect, and compassion.
As can be easily concluded from the above, for a while now I've been very inwardly focused.
I've made progress on some key areas: GTD, fitness, fear, insecurity, will power, assertiveness, and focus. While still "in progress", I know the improvements are pronounced enough to affect changes I myself have noticed in things like my average comfort level across a variety of situations, and even punctuality.
In mid-April I went to New York City to see my sister in a play ("Paris Commune" at The Public) and ended up packing nearly hour with various informal meetups and appointments. The part that stood out for me personally, besides getting to meet and hang out with great friends old and new, was that I made it on time (often with many minutes to spare) to every appointment. Doing so consistently for a week was a total first for me, and IMHO is a reflection of increased abilities in the areas of will power, assertiveness, focus and having a better sense of time's flow. Perhaps the pulse of NYC helped. By no means have I conquered punctuality for good, however I feel it is finally within my grasp.
March and April were very much months of transition for me, to make key decisions, be more assertive, be more spontaneous, and be more open about recognizing and openly declaring my own limitations to friends and business contacts, especially limitations to do with expectations, obligations, and dependencies.
In continuing with this transition, I've realized that it's time to turn that inward focus outward. The Data Portability meetup hosted by LinkedIn (thanks to one of the leading microformats implementers Steve Ganz) really helped me realize just how much work there is still to be done with making microformats as easy to understand as possible, not just for publishers and implementers, but for users as well.
I've decided to immediately increase my travel to spend more time with those that matter to me, and share the messages on the efforts I care about.
I'm looking forward to the next couple of months. May for me will be a bit of a microformats sprint. I've already arranged meetings with a major software company on Friday. Workshops in New Zealand after that, and issue resolution meetups when I return to San Francisco. June will bring more travel, with BarCampSeattle, and a return to San Francisco with the Supernova Conference (get tickets before a) prices go up, and b) it sells out!), for which I have the honor of chairing the "Open Flow" track. Coincidentally the book I'm currently reading is titled "Flow", thanks to my new super friend Tara Brown, who somehow knew exactly where my head was at and gave it to me to read just last week. It's a really good sequel in many ways to David Allen's Getting Things Done that I previously mentioned. Give them both a good read, try incorporating elements of both into your life, and then let's chat.
I've seen numerous people twitter wondering what to pack for SXSW today. Per my communication protocols, I'm blogging my answer. Note: I'm basing this purely on my personal packing list, so if you're a girl, or wear something other than black, you may want to check other suggested packing lists as well
If you are one of those urban superheroes that walk around with useful gadgets like swiss army knives (or any kind of knives), and allen wrenches (or anything that looks like it could be used to take apart an airplane), remove them from your utility belt, your jet pack, and any other part of your supercostume. Unless of course you're willing to pack a bag to check-in (which I highly recommend avoiding, due to risk of loss etc.).
The key to being prepared is wearing the essentials. This seems obvious but perhaps that's why it comes next.
Fill your pockets with:
With the above outfit, you're fairly set to survive a variety of temperatures, climates, and social situations. However, you really need a few more things to make it through an event as geeky and lengthy as SXSW. Pick out the items (or their equivalents) from below, and then find a small (yet robust) backpack / messenger bag like thing (I prefer Boblbee backpacks) that will fit them, and will of course fit fully underneath the seat in front you.
The above is pretty minimal for a four day conference. If you want a bit more flexbility in outfits, or are staying through SXSW Music, you're going to need to pack another bag, and might as well make it a rollaway. In addition to shifting the clothing, bath kit, and perhaps some of the powersupplies from the above to the rollaway, you'll want to include:
Start with that and iterate. See what you missed having with you this year, make a note of it, and bring it next year. Finally, if you lack any of the above, call your hotel and ask them for their "shipping address" (typically it will be "Attention: Your Name" followed by name of hotel and their normal address). Then order whatever you need from Amazon.com and have it shipped overnight or second day air directly to you at your hotel.
A year ago I published Three Hypotheses of Human Interface Design which in short provided some analysis that demonstrated that the simpler and faster a user interface is, the easier it is to use. The response has been quite amazing, with over a hundred blog posts and comments across various sites (Digg, Reddit etc.)
I was particularly humbled that Ev Williams incorporated a summary of the three hypotheses in a few of his talks last year: Web 2.0 Summit (referencing slide) and LeWeb 3 conference (see video discussion starting at 6:00). Ev is the rare "serial entrepreneur" that can be proud of that label, having successfully founded and sold two innovative ground-breaking companies (Blogger, Odeo) and now working on Twitter, a feat far more impressive than a few hypotheses in a blog post.
Last year when I posted The Three Hypotheses, they very much helped me explain why I was finding email so much less useful/usable than instant messaging (IM) and Twitter. Since then, I have found that while I can keep up with more people contacting me over IM and following more people on Twitter, email has simply become less and less usable, but not for reasons of interface, as I'm using the email application now as I was a year ago.
I'm probably responding to less than 1 in 10 emails that are sent directly to me, even fewer of those that are sent to a set of people or a list. The usability of email for me has deteriorated so much that I exclaimed on Twitter recently: EMAIL shall henceforth be known as EFAIL.
I think there are a number of factors why email is failing for me while other communication methods such as IM and Twitter are scaling. However, I think two specific reasons in combination account for most of the problem.
All forms of communication where you have to expend time and energy on communicating with a specific person (anything that has a notion of "To" in the interface that you have to fill in) are doomed to fail at some limit. If you are really good you might be able to respond to dozens (some claim hundreds) of individual emails a day but at some point you will simply be spending all your time writing email rather than actually "working" on any thing in particular (next-actions or projects, e.g. coding, authoring, drawing, enjoying your life etc.) and will thus experience a productivity failure. The obvious solution is to push as much 1:1 communication into 1:many or 1:all forms such as public blogs and wikis. My CommunicationProtocols wiki page describes this preference.
However, while 1:1 email is not scaling for me, I feel like 1:1 IM is scaling which would seem to refute the above reasoning. There are two reasons why this is not so:
The second reason that I think email is becoming a worse and worse problem is directly due to its higher usability barrier, that is:
Email requires more of an interface cognitive load tax than IM (as compared to the time spent on writing the content itself), thus people naturally put much more into an email (perhaps in an unconscious effort to amortize that interface tax overhead across more content). People may feel that since they are already "bothering" to write an email, that they might as well take the time to go into all kinds of detail, and perhaps even add a few more things that they're thinking about it. Such natural message bloat places additional load on the recipient, both in terms of the raw length of the message, and in terms of the depth and variety of topics covered in the email. This results in a direct increase in processing time per email thus making it even harder for people to take the necessary time to process and respond. I know I've left numerous emails grow stale because there were simply too many different things in the email that required a response, and I didn't want to send a response without responding to everything in the email because then I would inevitably receive yet another email response without being able to file the original as being processed and thus have the situation worsen!
I don't have answers to all of these problems. I do have some suggestions that appear to be helping, though I'm far from solving the larger problem of scaling communications in general.
My personal wiki turned one year old today. That was fast. As I've picked up and used additional tools such as a wiki, Twitter, and perhaps most recently Pownce (congrats on the public launch BTW!), I've found that each serves a specific purpose in my life, and that's ok, there's no need to try to force each to be all things. See my "Identity facets" sidebar for the full list of sites I'm currently actively using for various publishing purposes.
My wiki (hosted by the nice folks at PBWiki) has mostly served as a place for me to record notes, incomplete thoughts, works in progress that may help other folks out. I've also used it as a place to keep current contact information, work on some collaborative efforts (such as the upcoming Body Optimization session at SXSW 2008), and other projects.
It's also a place I've kept notes or documents that I expect to keep current / update in place, as opposed to blog posts, which are more like snapshots of thoughts in time. For example I put bug reports and feature requests on my public wiki, rather than hassling with the login and TOS hurdles of the myriad feedback systems of the products and services that I use.
I've shared my wiki password with a few friends, a few of whom have made edits/fixes here and there. I'd like any friend or colleague that I'm currently collaborating with on a project to have access, so, contact me for the password.
I've found a personal wiki very useful for publishing information that I felt needed to be published but couldn't quite figure out where to put it. The beauty of it is that if/when I do later find a more "proper" place for the information (such as a feedback forum on a product site), I can simply put a URL to the page with the information on my wiki, which I can then update as necessary without worrying about checking yet another forum site.
I recommend that everyone start their own personal wiki for capturing and updating these kinds of random thoughts. Go to PBwiki.com to get started.
My journey implementing and/or iterating/improving/creating "open" standards began almost 10 years at Microsoft when I was assigned the area of CSS support in Internet Explorer for Macintosh. Along the way I've learned a lot about the longterm value of open standards, open source, and open content, and as a result the plethora of "open" licenses out there. Having seen real difficulties that different "open" projects have had working together due to license (or even philosophical definition of "freedom") incompatibilities, limitations, friction, barriers to developing derivative materials to help "open" projects, and even FUD used inside many corporations to limit use of "open" resources, it led me inexorably to one conclusion.
If you want your "open" project to be as open as possible for maximum benefit and reuse, you have to (a) release it to the public domain, and (b) depend on the community for strength of cohesion and identity. Both are important, and only recently (the past few years) has the latter been made truly possible by the Web, blogs, and real-time search and update services.
Perhaps the most common question I've been asked in response is whether I'm worried about someone (or some organization) taking such material in the public domain and "abusing" them, whether creating a incompatible variants (of formats), forking, commercially benefitting etc. The latter is the easiest to address. Standards work best when there is commercial incentive to implement them and implement them interoperably. The former aspect requires analyzing underlying assumptions.
The implicit assumption in the questions of the form "what if someone/something takes your work and does something bad with it" are as follows:
Rather than grasping at the false sense of security that copyright or other IP protection seems to afford, the irony is that it is actually stronger to affirm and accept that for practical purposes (given time and costs of enforcement) there really isn't much IP protection available to individuals or open source projects, and thus you must depend on the community built around the standard. This open acknowledgment of dependence on the community and absence of any other support provides much more open incentive for the community to stay cohesive, rally around, and strengthen itself in order to preserve the openness and fidelity of a standard.
Thus, on this "Public Domain Day" as noted by the Creative Commons blog, I encourage anyone and everyone creating or developing an "open standard" or "open data format" to do so completely in the public domain.
If you're going to start a new wiki, whether for a new web standards effort, or for a random community topic, consider requiring that all contributions be placed into the public domain. The Body Optimization wiki (first to do so AFAIK) notes this requirement in its PBWiki login form with a reference to the Creative Commons Public Domain license (CC-PD), and has so from its inception.
If you are leading an existing "open" standards effort, whether for a data format or protocol, I encourage you to strongly consider doing what we did with microformats:
Everyone that works on any open standard can make a big difference to the greater body of open standards that all of us depend on to freely build use and iterate upon tools that interoperate. Make it one of your new years resolutions to either take the leap to public domain with your open standards efforts, or at least take some of the above-noted concrete steps toward doing so, and make your open standard as open as possible.
It's been quite the eventful year, so perhaps it is only fitting that a couple more big things got squeezed into the last few days.
As of December 29th, all new contributions to the microformats wiki are required to be released into the public domain. This has been a project that I've been working on for microformats for quite some time, was much harder and took much longer than expected, and was really important to me personally.
See the blog post on microformats.org for more details, reasons why, and historical events leading up to this first of a kind decision to make a standards effort as open as possible.
Aside from the party going on (that I'm briefly hiding from to write this up), this year concluded for me with LifeCamp, a BarCamp/Foocamp-like event 12/30-31 that focused on one question: What are you doing with your life?
My friend Julie and I thought this up when discussing end of year rituals, and threw it together quickly and roughly in a matter of days (like the first BarCamp). We invited a bunch of people (also coarsely brainstormed, certainly not comprehensive), a few of whom were actually available to attend, and shared an incredible two days of reflection (what did you do) and projection (what are you going to do).
We quickly decided at the start to make the event both off-the-record by default (similar to Foocamp and a few other such conferences) and even fairly "in-confidence" to create a more comfortable and safe environment for sharing personal, sensitive, and vulnerable aspects of ourselves. However we also decided to very much document the abstractions about the event, in the hopes of improving the replicability of the event, both for ourselves, and for anyone wishing to organize a LifeCamp in their own town, with a few of their trusted friends and colleagues. Check out the LifeCamp wiki.
I've got more thoughts on the microformats example of making open standards as open as possible, and the LifeCamp variant of Barcamp that I'll post in the new year. For now, there is champagne and sparkling cider to hand out.
Happy New Year and see you in 2008!
It's not every day that construction equipment literally crosses your path. This particular bulldozer was clearly just entering the job site to get some work done.
I have no idea where we were or what we were doing, but my friend April who I had just met at SXSW, was wearing a t-shirt that said big O little o and while I first thought of the computer science notion of big O vs. little o, I had a feeling that's not what the shirt was about. So I asked her to explain it.
Update: April has reminded me that I recorded this at the "im in ur web2open partyz drinkin ur beerz" party this past April, where I also met iJustine.
This past April I had the fun experience of getting in touch with a college pal who I had not seen or heard from since then. In short: we lived in the same dorm at Stanford one year during which time we did a bunch of things like go for motorcycle rides etc. but the most memorable was attending a Apple Holiday Party together (I was an intern at Apple at the time) and being surprised with a private performance by Ella Fitzgerald (yes the) - one of her last performances. Yes that's the kind of party Apple used to throw, even a private one just for employees.
Being Stanford types we both just got super busy and lost touch after that year. Fast forward to this year. Robin found me on the interwebs, and we ended up grabbing a bite together in LA and catching up on many years since we last saw each other. Our lives had taken very different paths, and over the course of the evening she made me explain how the internet came about. To see if I had made any sense, and see how well she retained it, I made her summarize the history of the internet for me in 30 seconds (actually 40, but what's 10 seconds among friends?). Judge for yourself, I think Robin did quite well.
View blog reactions
View blog top tags
Technorati Top Searches
Technorati Top Tags
