Monthly Archives: May 2007

Software Design: Grant Peace of Mind

I understand about indecision But I don’t care if I get behind People living in competition All I want is to have my peace of mind – “Peace of Mind”, Boston Avoid Indecision, Grant Peace of Mind If you are a software designer, your goal should be to have every page have one purpose. This […]

Google Gears

Google Gears Google Gears javascript libraries transparently create and update a local database. Developers simply execute SQL against a local database. Google Gears’ database module takes care of prompting the user for permission, creating the database, and executing the SQL. Google Gears also provides a local server module to cache web content and then serve […]

Destroy…transform…condense…make it more substantial.

”When you begin a picture, you often make some pretty discoveries. You must be on guard against these. Destroy the thing, do it over several times. In each destroying of a beautiful discovery the artist does not really suppress it, but rather transforms it, condenses it, makes it more substantial.” – Pablo Picasso Code that […]


I have just returned from three days of RailsConf 2007 in Portlant, Oregon and wanted to share my overall impression of this very well-done event. There were four tracks, so no one could have attended all sessions. So, I won’t be sharing a play-by-play summary of each of the sessions. The guys over at […]

Starbucks Everywhere

In most airports this space between the “up” and “down” escalators would be an unoccupied, dusty corner. Not here at Portland’s airport. btw I’m here for RailsConf 2007. Full reports on the next three days of geek-speak to follow.

Design Decision: Tags

Sometimes a slicker ajax-y UI is not the best choice. For instance, every LeadsOnRails contact can be tagged with an unlimitted number of tags. To add a tag, users either enter a new one in a text box or select an existing one from a drop-down box. An alternative design would have been to use […]

Design Decision: Learning the Blank Slate Approach

The Blank Slate 37signals’ Getting Real has a section on The Blank Slate. The Blank Slate stage is that stage of an application or screen in which no or very little data has been populated. The problem is that most designers design around a fully populated screen. And though that may be how the user […]