Usability: October 2007 Archive Page

In a corner of the living room between the couch and the video tape cabinet, my kids keep a huge stash of paper towel rolls, which they use to stage epic battles.

The Cardboard Tube Fighting League website is annoying since it's mostly made up images... I didn't find any text that I could copy and paste here.

Web guru Jakob Nielsen risks the wrath of the grammatical bluestockings when he suggests that the passive voice might be useful for headlines, but he's really talking about front-loading web titles, so that the first two words of a web heading will contain words that will catch the eye of people scanning the page. Since people usually search for concrete nouns, rather than verbs, it makes sense to get those content keywords in a prominent place.

Words are usually the main moneymakers on a website. Selecting the first 2 words for your page titles is probably the highest-impact ROI-boosting design decision you make in a Web project. Front-loading important keywords trumps most other design considerations. Writing the first 2 words of summaries runs a close second.

Nielsen got plenty of attention for this claim, but it's a bait-and-switch. Passive sentences are not the only way, or even a particularly good way, of getting subject words to the beginning of web headings.  Consider "Passive Voice Can Boost ROI in Web Headings," or "Passive Voice: Surprisingly Useful in Web Headings." 

Also I cringed at one of Nielsen's examples of a good, scanning-friendly use of the passive voice: "13 design guidelines for tab controls are all followed by Yahoo Finance, but usability suffers due to AJAX overkill and difficult customization."  If somebody alphabetizes all the page titles on a website, that page is going to be alphabetized under "13."  

Professional writers know that the most meaningful part of a sentence comes at the end, when you're setting up for the idea that follows.  So the most significant part of this particular sentence is not that 13 design guidelines for tab controls were followed, but rather that other design choices hurt the site's usability.

For the past year or so, my main job in our homeschooling family has been to teach Carolyn (5) how to read. Now I've picked up the task of teaching Peter (9) computer programming.  Last week I wrote a few simple BASIC programs to teach a very basic concept that some of my college students have trouble with when I teach interactive fiction programming -- the fact that when you write code, you have several different audiences -- not just the computer, but the user and also yourself (or some other programmer who inherits your code).

Last week we did a quick-and-dirty choose-your-own-adventure story, and showed Peter how to copy-and-paste blocks of code for editing, rather than retyping long sequences all at once. Several times I made a deliberate mistake, and pretended that I didn't know how to fix it. Peter picked it up quickly.  He was not so good at picking out problems such as missing punctuation or the difference between spaces and underscore_characters, so it was slow going at first.

I do plan on beginning each coding session with a little bit of text-based BASIC coding, but he has started saying, "Daddy, is this enough? Can we move on to Scratch now?"

Scratch is a wonderful 2D animation environment that is designed to introduce kids to programming concepts.  Think of it as Flash for kids. Each element of the programming syntax (an if/then statement or a repeat loop) is graphically represented like a puzzle piece, and the various elements of the program snap into the blocks, giving a tremendously satisfying visual feedback when the programming syntax works.  You'll never see an "error" message when you are working with Scratch -- the pieces just won't fit together if they don't go together. Instead of the "alpha" value, graphics have a "ghost" value, which is a far more sensible name. (I remember being very frustrated when I first started experimenting with creating textures for 3D games, because none of the tutorials I could find bothered to define such a basic term.)

Adding considerably to the charm factor is this collection of kid-produced Scratch tutorials that teach basic Scratch concepts. I downloaded one to see what it was like, and I downloaded a few more just because I think it's cute to hear the kids narrate the tutorials.

Students at Expo were beta testers for a new programming software called Scratch. Designed specifically for youth, it allows them to create their own stories, animations, fames, music and art. At the same time, they apply math concepts, design, problem solve and collaborate. To learn more about Scratch or download the program yourself, go to . One of our writing standards is to explain how to do something. We had so much fun with the Scratch program that we decided to make computer tutorials so others could learn the basics, too. Click on a link to see what you can do with Scratch!

Utterly pointless, and at the same time completely brilliant. You can only eat a few spoonfuls of cereal at a time, so why not keep most of the bowl dry, and soak only a few bites at a time? From eatmecrunchy.com.

TiddlyWiki is a complete wiki in a single HTML file. It contains the entire text of the wiki, and all the JavaScript, CSS and HTML goodness to be able to display it, and let you edit it or search it. Without needing a server.

I played with TiddyWiki a bit, but wasn't able to edit the pages in my browser, as promised. Perhaps the ad-blocker or some security feature on my browser is interfering with the operations. I'm blogging this so I can go back to it later.

A Yahoo! developer reflects on the missed opportunities caused by the economic demands of the recording industry:

If the licensing labels offer their content to Yahoo! put more barriers in front of the users, I'm not interested. Do what you feel you need to do for your business, I'll be polite, say thank you, and decline to sign. I won't let Yahoo! invest any more money in consumer inconvenience. I will tell Yahoo! to give the money they were going to give me to build awesome media applications to Yahoo! Mail or Answers or some other deserving endeavor. I personally don't have any more time to give and can't bear to see any more money spent on pathetic attempts for control instead of building consumer value. Life's too short. I want to delight consumers, not bum them out. If, on the other hand, you've seen the light too, there's a very fun road ahead for us all. Lets get beyond talking about how you get the music and into building context: reasons and ways to experience the music. The opportunity is in the chasm between the way we experience the content and the incredible user-created context of the Web.

Philipp Lenssen and I had a bit of fun imagining what an early, early draft of the Google home page might have looked like.