From the monthly archives:

February 2004

too much caffiene

February 23, 2004

in Food, Links, Reviews

There’s a rant on Salon today about the Starbucks booklet that came out recently that explains how to order coffee. The author of this rant positively has a fit over it, and uses the booklet as a jumping-off point for the usual Starbucks-is-the-root-of-all-evil discussion.

I drink Starbucks coffee (grande decaf nonfat latte). I also drink Peets coffee (medium decaf nonfat latte). Mostly I drink coffee from the Los Gatos Coffee Roasting Company, because it is close and because it is good (double decaf etc etc ) and because I like the people there (and also they have screamingly fast free wifi). But the coffee chains do not bother me. I do not get excited about the exact flavor of this coffee over that coffee, of french roast over expresso roast, or the politics of chainness over localness. I like coffee. I like coffee a lot. Wish I didn’t have to drink decaf, but thanks to the wonder of psychotropic medications I’ve ended up being hugely sensitive to caffiene, and a full-strenth latte is not a pretty thing, mostly for people who have to be near me as I babble incoherently at them for a couple hours. Even decaf, for me, has enough caffiene to buzz me hardily. But now I’m off-topic.

I got the Starbucks how-to-order-coffee booklet in with the Sunday paper this weekend. Contrary to Mr Salon Ranter I thought it was kind of cute. Its printed on nice card stock. It sits comfortably in the hand. The writing is kind of precious, and many of the definitions were obviously bogus (“unleaded” is how you order a decaf? Who the hell orders decaf as “unleaded”? Not anyone at any Starbucks I know) but overall I believe it was a success at marketing to me. I learned stuff (I’ve heard people order dry caps at coffeshops, not just Starbucks, and never knew what that meant), and although I have zero intention whatsoever of ordering a peppermint latte (yuck!) I do know now that I can get one if I should someday become insane. So I vote on the side of thumbs up for the Starbucks booklet.

Another reason I like the booklet concept: if it helps people get through the Starbucks line faster, rather than getting up to the top of the line and then standing there and staring at the menu and going “uhhhhhhhh…” then I am all for it.

Of course, one could make the argument that it’s just coffee, it is not the DMV, and of course as a good technical writer I should understand that if a product as simple as coffee needs a manual to explain it than perhaps its UI has been made overly complex in the first place.

But then I’d be ranting, and I promised not to do that.

{ Comments on this entry are closed }

cycling stigmata

February 23, 2004

in Personal, Stories

I went on a 30 mile bike ride on Saturday (got rained on, it sucked, whine). Did a full hour and a half of spinning on sunday, plus an hour of weight lifting. Did another 45 minutes of spinning first thing this morning, at which time I started spontaneously bleeding from the knees.

Close inspection showed that I was not, in fact, having some kind of bicycling ecstasy manifesting itself in knee stigmata. Instead I had some road rash from a few weeks back that apparently had retained some grit, that that grit was working its way out from under the skin.

Ew.

At any rate, I think random bleeding is generally a good sign that one should take a day off.

{ Comments on this entry are closed }

wierd technical writing

February 20, 2004

in Reviews, Tech

I’m always interested in new and strange ways of teaching people about technology, and I’m particularly amused by bizarre computer books. Yes, I read this stuff for fun (why are you staring at me like that?)

For example, Head First Java teaches Java with cartoons and wierd jokes. It is totally brilliant.

Stealing the Network, on the other hand, is straight-up text, but its also unique. It teaches network and computer security through a bunch of short stories. The quality of the writing as fiction isn’t stunning, but because there are characters and dialogue, the situations are engaging and interesting and the technology is thus easier to absorb.

Online there are always a lot more examples of unique technical writing, and today’s example that inspired this post is Why’s (Poignant) Guide to Ruby. I’m not sure this guide actually teaches much, but its certainly interesting and a lot of fun to read. Kind of a surreal stream-of-consciousness thing. With cartoons.

I admit, I am a real sucker for cartoons.

{ Comments on this entry are closed }

the cold that would not die

February 20, 2004

in Links

Mercury News | Persistent colds won’t go away

Ah, this explains why I can’t get rid of this beastly cold. Dammit. (thanks to Educated Guesswork)

{ Comments on this entry are closed }

freshly squeezed emu juice

February 20, 2004

in Links

Daftman Technical Manual for the NM-156 Reciprocating Emu Press (a 990K PDF file)

I’ve had a link to this this sitting in my email for a while (from the tech writer’s mailing list (yes, there is a such a thing, and yes, most of the time it is just as dull as it sounds)). I only looked at it today. I’d really like to know the story behind this.

{ Comments on this entry are closed }