Friday, March 30, 2007

Kathy Sierra

Once upon a time I met Kathy Sierra at a weird mini-conference at my former employer. I really enjoyed her talk, and I have followed her blog since then. I am amazed at 2 traits of her blog (ones I wish I had), first is great graphic design. Stock photos and tablet drawings of pie charts never looked so good! Secondly, every post is part of a excellent narrative and is argued well. Representing no doubt years of research.

Of course by now you have probably heard of the whole death threat bit. I really didn't know what to think when I saw it, but I certainly did not want to write a blog post using the world 'but'.

I don't think anyone can really know what Kathy is feeling. Having met her, and knowing she is on the straight and level, I am inclined to believe her. I do think that contributions indicating that people should "toughen up" really don't help much. Especially when coming from a position of privileged and protection.

Those are easy to dismiss - however what is harder to dismiss is the use of the word 'but'. I really don't like this word, and to illustrate why, I will do an example:

"I support your cause, but I am concerned that ..."

Now lets replace the but with it's true meaning:
"I support your cause, but ignore everything before but, since what follows are my true feelings, I am concerned that...

This is my own cognitive search-and-replace, your mileage may vary, results aren't guaranteed, etc, etc.


For no specific reason I was reminded to dig up the h4x0r economist "comics". Any comic where Greenspan speaks leet is pretty much gold in my books.

Wednesday, March 28, 2007

Two Cool videos

I want the following UI interaction devices on my desk and in my bag. The first is a new desktop UI metaphor, based on physics. The second is a multi-touch display, sort of like Minority Report and Star Trek.

YouTube Link

Google Video Link

Tuesday, March 27, 2007

Lunch Hosting In Kirkland

Once nice thing about working here, is it is very easy to convince people to come visit you for lunch. The famous Google lunch, free, and filled with smart people who love to chat. Who could want more? Today I had my ex-coworker Alexy come by. He had some photography tidbits, a cool Leica point and shoot, and plenty of "financial engineering" to talk about. Cool guy, he is currently ramping up to a PhD - good luck there.

Also he owns of all sites. Crazy guy.

Friday, March 09, 2007


Thanks to the sweet hook up, I have a Joost account now.

Review forthcoming.

Thursday, March 01, 2007


On the subject of design, many people have many things to say about it. Of course, with such a highly debated topic, how can one think they are possibly smart or qualified enough to say more on this subject?

The hubris of developers pretty much demand that we should talk about crap we don't know enough about. Of course there has been much writing about how a "child like approach" can bring a fresh look and new innovative ideas. To that end, I think I have noticed some things about great design that I think is truly new (to me). I'm not sure I can condense my list in to an actual list, so you get prose instead.

Great design generally comes out of inspired creativity. You rarely can force such creativity, which is why those ad companies are paid the big bucks. You rarely get this kind of creativity out of groups, and never out of committees. If you have a small design team that operates in a high bandwidth communication situation (ie: in person) and they "think like one" you may end up with amazing things. Design to completion though is fraught with compromises. Some compromises are ok, others are critical junctures where your design just got shot to hell. I don't know how to differentiate between these two types of compromises.

Every design has essential elements - any changes that detract from these elements end up taking away from the overall picture. Since the essential elements, or first principles, can be unknown to everyone, great designers also end up being great dictators. Since you can't effectively argue about first principles you don't know or can't communicate, you are left with force of personality (see: Steve Jobs).

There are however first principles of great design. Things all great designs have. All designs come from simple ideas that can end up having complex interactions. A great example would be Hypercard. Years later people still rely on hypercard stacks for various things. The iPod is a classic design study, so all I'll say about that is the central idea is "I should be able to hold all my music in one hand". The simple idea must not be a mission statement, it must reflect a functional piece of the design. A counter example would be "the user should be able to manipulate all manners of information" - this is more of a use case or end goal, rather than a design principle.

Since design principles reflect the working or physical aesthetic of the product (see: chair design), they should ideally reflect a subtle or even sublime balance between functionality and simplicity. Simple first principles that allow rich functionality is hard to achieve however. However, simplicity sometimes just ends up in overly simple system, where the basic rules fail to interact in interesting or meaningful ways. One possible test is the orthogonal test - each first principle should be completely free from the others. By combining multiple simple rules you end up with a rich multidimensional space in which aspects can be combined.

The basic bench-test for designs is often the gut or intuition test. This may return conflicting or shallow results depending on the strength of the intuition involved however. This article has suggestively been about general design, but my overall concern is primarily with software design. The goodness of a software design seems to be escaping many people, unlike, say, Architectural design. There is an increasing focus on this subject over the last 10 years, with many new players such as 43 folders. However, this is leading edge stuff, not being taught in school or being spread widely enough in the engineering space.

Perhaps one of the biggest obstacles is the intuitive portion of design. Although intuition is just short for combining many disrelated factors in a semi-unconscious manner, the left-brained focus of many software engineers can leaves them opposed to this approach. Perhaps some software engineers can benefit from right-brained activities? Drawing, musical instruments and other artistic endeavors can trigger right brained thinking. I am blessed (cursed) with an extremely right brained thinking style, which oddly enough gives me good grades in math, but bad grades in organization (you should see my apartment!).