cucumber and tomato salad with basil
zucchini/eggplant/cabbage/onion ratatouille
tomato surprise
grilled corn on the cob
carrot cake
roasted beets, zucchini, and summer squash
coleslaw
squash/tomato pizza
bread and butter pickles

Thursday is farm share day, when we get a box full of veggies from Brookfield Farm.

Here’s what’s in my fridge right now:

3 lb summer squash
3 lb zucchini
2 heads lettuce
4 lbs tomatoes
1 head white cabbage
1 head red cabbage
unidentifiable herb
1 head bok choi
4 heads baby bok choi (“I want my baby bok, baby bok, baby bok…”)
1 bunch kale
1 bunch beets and beet greens
1 bunch Italian parsley
garlic scrapes
3 eas corn
2 onions
2 bunches scallions
green bell pepper
1 bunch celery
dill
1 lb bing cherries
2 lbs carrots
3.5 lb gigantic cucumbers

Open source usability is indeed a major problem—I think it’s the biggest thing that has kept the Linux desktop out of most hands. With so many coders switching to Mac OS X, we know that even people in the software industry avoid it. It’s a shame that the Linux desktop is not so easy to use, because the community has put so many hours into the development of projects like KDE (which describes itself first as easy to use, right on its front page). I often feel that the community has made a bed which it is now avoiding.

One problem is that open source is largely about cloning commercial software and then adding features. Many developers add one or two features they want for their own use, incorporate their changes back into the source without a thought to the utility of, or excise created by what they’ve done (Luis Buñuel: “Every object conceals another.”).

We don’t need more features. No one wants a system with 34 buttons in the administrative part of its file brower, or 28 options on its main menu, 16 of them being submenus that beg questions like, “What’s the difference between Office and OpenOffice.org?” or “To change my desktop background, do I go to Settings, System, or Utilities?”

People typically have a pretty small set of tasks they ever want to perform with a computer program, and the variety from person to person isn’t that great, so what we need is fewer options. You might propose that we just remove some features, sculpt the software into perfection, and we’ll be all set, right? This is what Frans Englich proposes in a recent article on NewsForge. I think this approach would help, but I don’t think it’s the answer. We can incorporate a lot of options if they’re presented in an organized, hierarchical (some options more strongly emphasized than others, many options hidden away for only the most advanced power-hungry users to find), and intuitively obvious way that is consistent and cuts across the entire system.

Usability starts broad and goes down to the core, within and between software; it is not just the fine patina at the surface. Though sculpting current software down to a simpler form that addresses 90% of the typical user’s goals may help, I think great usability is thoughtfully considered throughout the development cycle.

This is how Apple has been so successful when it comes to usability: they’ve chosen to design and control every level of the experience, not even stopping at the edge of your desk. Apple is practically designing a lifestyle. Their individual compontents are easy to use and consistent with each other, and the interaction between components is clear and consistent. Usability considerations aren’t constrained to one program. Apple’s approach doesn’t just go to the core of software, it goes to the core of all software and hardware in their system and to the global APIs that are available in all software. A thorough style guide means that keyboard shortcuts in one program that are consistent with keyboard shortcuts in another, and so on. So while you may look at a small change in source code and say “this makes my program more (or less) usable”, this is not a strategy for great usability in my opinion.

I do think we can have usability in the open source community. Making incremental changes to individual pieces of software won’t cut it, however. I believe that (yet again) a new Linux desktop/distribution should be formed, with usability as its purpose, and with the following goals:

• Maintain interface consistency within and between all components. No software should be allowed in without meeting these criteria, and no more than one program of any kind is allowed (unlike today where there are five options for MP3 players, etc.). This kind of consistency is best achieved, in my opinion, by an auteur—someone who provides the central vision, and acts as gatekeeper and high-level decision maker, just as Linus Torvalds has done so successfully with the Linux kernel.
• Severely limit or reëmphasize the options available to the user. We’ve already got way too many choices in this world. Lets reduce interface excise, hide or remove the least-used options, give greater emphasis to the most-used options.
• Require all programs to use consistent keyboard shortcuts, preferences, operating system functions (like cut and paste), the same file browser, and so on. Make overarching OS-level decisions about the direct manipulation of data, so that this is consistent across all programs. This isn’t just about drag and drop, it’s also about spell checking, renaming things, etc.
• Waste no pixels, leave as many as possible for content, use as few as are needed for interface.
• Prevent crashes by allowing only mature, low-bug software (the Debian approach)
• Make it comfortable for my grandmother or the hacker next door. Comfort requires the OS to become a part of the person using it, to take on the user’s personality. A new user should be able to quickly settle into the system and feel good using it. After all, the goal is to make the user feel productive doing whatever it is they’re doing, and productivity is just as much an emotion as it is an internal measurement.

There are more items on this list; I don’t know them all. A usable Linux desktop will need a lot of thought before it gets off the ground. I think it will need a clearer statement of the goals, a thorough style guide, and so on. This project could be greatly informed by other style guides and usability books, but it also needs to be tailored to the nature of open source development.

If executed properly, I think the final desktop environment will be far and away more usable than the mess we have today. Now, who wants to write up a vision statement? ;-)

Last Sunday I visited iggy’s “factory outlet” store in Watertown. They sell super fresh bread and pastries of all varieties, many of which they don’t distribute to local stores (no Shaw’s would know what to do with one of their 2 foot long crazy huge rustic loaves, for example). But I avoided the exotic stuff, cool as it looked, and instead got the standard loaf I usually get from them, a small francese, which, as far as I can tell, is the same as a ciabatta.

I’ve always noticed a distinct difference in the flavor of Iggy’s bread that I couldn’t put my finger on. A word did come to mind on Sunday, though: saffron. Is it possible that they add saffron to their bread? Had I discovered the great Iggy’s conspiracy? Probably not. I bet they just have superior flour. But I couldn’t get the saffron out of my head. So today I made a saffron ciabatta, just to try it. I ground up a scant 1/4 tsp of saffron and mixed it with a couple tablespoons of boiling water, waited about 10 minutes for it to “brew”, then mixed all of this with the rest of the water for the final build of the loaf.

I took it the first loaf of the oven about an hour ago, and I just ate a couple slices of it. The saffron is definitely present, and I think the overall flavor is subtly better than previous ciabatta. It’s at least as good as Iggy’s, in my opinion, but I’m biased because I made it and it’s much fresher than I could ever get from Iggy. Technically my loaf (and perhaps Iggy’s) is unorthodox in that it strays from the standard water/flour/yeast/salt of white bread, but I don’t care. It’s tasty.

roundabouts in America
the magic roundabout in Swindon, UK
RoundaboutsUSA, the site dedicated to free traffic flow through the design and use of roundabouts.