Culture

Samoas versus Caramel deLites

My favorite Girl Scout cookies are unquestionably the Samoas (Thin Mints and Tagalongs are also quite good, but nothing compares to the mighty Samoa). Several years ago, I went to purchase a box and was surprised to learn that they changed the name to Caramel deLites. And they seemed to taste different too! It didn’t take long to notice that Samoas were still being sold, and as it turns out, there are two commercial bakeries that are licensed to make Girl Scout cookies. Little Brownie Bakers have the strange names that we are nonetheless familiar with: Samoas, Tagalongs, Do-si-dos, Trefoils, etc… ABC Bakers are much more prosaic and descriptive: Caramel deLites, Peanut Butter Patties, Peanut Butter Sandwiches, Shortbread, etc…

Generally, both bakeries are pretty good, but the question is, what are the differences and which are better? Let’s take a look at Samoas versus Caramel deLites.

Caramel deLites and Samoas

The Caramel deLites are on the left, and the Samoas are on the right. As you can see, the Caramel deLites have a somewhat lighter color to them, and that’s partially because they use milk chocolate as opposed to dark chocolate. Wikipedia says they don’t have as much caramel as Samoas, but I’m not sure about that. Personally, I think they’re chewier than Samoas, and if I had to choose, I’d choose Samoas. But maybe I’m just weird. I asked around, and there didn’t seem to be a consensus. Some people loved one variety, others loved the other, most were indifferent.

So I did a test. I put one box of each on my desk, removed any identification, and put a note up that asked people to try one of each and vote for their preferred cookie. This was a single blind test, and the cookies were labeled only A and B. Ok, so it was hardly a stringent methodology and a lot of people knew which were which just by looking at them, but in the end, it appears that Samoas have a slight edge. A sample size of 8 people is statistically significant enough for me, and it came out 5-3 in favor of Samoas. So there, Samoas are empirically better than Caramel deLites. It’s scientific!

A couple of us also compared the Thin Mints (which are the only ones I know of that have the same name no matter what baker), but results were mixed. The cookies are clearly different, and the ABC Bakers (the ones with the prosaic names) Thin Mint actually seems more minty, but they’re both pretty good. No stats for this one, but anecdotal evidence suggests that people like the ABC Bakers version better. So there you go. They’re both good.

Incidentally, if you can get your hands on Edy’s® Girl Scouts® Samoas® Cookie Ice Cream, I highly recommend stocking up. It’s available slightly longer than the cookies are, but it’ll be gone by March, and it’s quite possible the greatest ice cream ever created.

Japanese Cootie Shots

One of the things that interests me about foreign films is the way various aspects of culture become lost in the translation to English. In some cases, this is due to the literal translation of dialogue, but in others it’s due to a physical mannerism or custom that simply can’t be translated. In a post about Lain’s Bear Pajamas in the Anime series Serial Experiments Lain, I mention an example of such a gesture that appears in Miyazaki’s Spirited Away. Of course, I got the details of the gesture completely wrong in that post, but the general concept is similar. Since Spirited Away is the next film in the Animation Marathon, I got the DVD and took some screenshots. The main character, a little girl named Chihiro, steps on a little black slug and the boiler room man, Kamaji, says that this is gross and will bring bad luck. So she turns around and puts her thumbs and forefingers together while he pushes his hand through (click the images for a larger version).

Chihiro

Chihiro

Chihiro

Now this is obviously some sort of gesture meant to counteract bad luck, but it’s a little strange. The dialogue in the scene helps, though the subtitles and the dubbing differ considerably (as I have been noticing lately). The subtitled version goes like this:

KAMAJI: Gross, gross, Sen! Totally gross!

(CHIHIRO puts her hands in the shape of a rectangle.)

KAMAJI (pushing his hand through the rectangle): Clean!

Quite sparse, though the meaning is relatively clear. The dubbed version expands on the concept a little more:

KAMAJI: You killed it! Those things are bad luck. Hurry, before it rubs off on you! Put your thumbs and forefingers together.

(CHIHIRO puts her hands in the shape of a rectangle.)

KAMAJI (pushing his hand through the rectangle): Evil… begone!

I noticed this gesture the first time I saw the movie, because I thought it was stange and figured that there had to be a little more to it than what was really being translated. On the DVD there is a little featurette called The Art of ‘Spirited Away’ and in one of the sections, the translators mention that they were baffled by the gesture, and weren’t sure how to translate it. After researching the issue, they concluded that it’s essentially the Japanese equivalent to a cootie shot. Of course, this makes a lot of sense, and it’s totally something a kid would do in response to stepping on something gross (this film, like many of Miyazaki’s other films, seems to nail a lot of the details of what it’s like to be a kid). It also illustrates that the boiler room man isn’t quite as gruff as he appears, and that he even has a bit of a soft spot for children. Interestingly enough, this gesture is repeated again by a little mouse (I think it’s a mouse), and the soot balls that work in the boiler room, though I don’t remember that (I’ll try to grab screenshots when I rewatch the whole film)

Again, Spirited Away is the next film in the Animation Marathon, and it’s probably the best of the bunch as well. Expect a full review soon, though I’m not sure how detailed it will be. Filmspotting (the podcast that’s actually running the marathon) is on a bit of a break from the marathon, as they’re doing their obligatory 2006 wrap up shows and best of the year lists.

Merry Christmas

In the future, pine trees will be extinct, and then what will we do for Christmas trees? We’ll use a cactus. I present you with this year’s Traditional Kaedrin Christmas Cactus:

Traditional Kaedrin Christmas Cactus

The picture didn’t turn out as well as last year (it keeps coming out fuzzy for some reason, perhaps because of all the extra lights or because of the lighting – hey look, a handy guide for taking pictures of Christmas lights), but it’ll do well enough.

Moving on, a few other christmas links for your enjoyment:

That’s all for now. Go forth, and watch your Anime.

It was only a fantasy…

I’ve never been much of a sports fan, but in recent years I have become a fantasy sports fan. The funny thing about fantasy sports is that it totally distorts the importance of events in games. Take, for instance, last week’s Monday Night Football game. We were nearing playoff time in fantasy football. My roommate and I were dominating the league, and had clinched playoff spots. There was one other team with a winning record who had also clinched. And there were 2 teams in contention for the final playoff spot.

It’s a head-to-head league, and I was playing one of the 2 teams. Due to some bad performances by key members of my team (*cough, cough, Tom Brady, cough*), I was down by 5 points by the end of the Sunday games. He had no players remaining, but I had 1 person playing in the Monday night football game. There’s just one problem: he’s a kicker – not a position known for high scoring. A kicker gets 1 fantasy point for every extra point they kick, and field goals can be 3-6 points (depending on how far the kick is from).

So basically, what you had last week was 4 or 5 people throughout the northeast intensely following and rooting for (or against)… a kicker.

Me: They’re in field goal range! Call in Wilkins!

Roommate: Dude, it’s second down. I don’t think they’re going to kick it.

As luck would have it, I lost. However, I was still in the playoffs and I ended up playing the same person I would have played anyway. Alas, it appears that my team peaked early. After going 12-1 during the first 13 weeks of play, I’ve gone 0-2 in the past two weeks. I lost in the first round of the playoffs. There may still be some hope for placing third place, but I must concede that my season didn’t end the way I planned. The main culprit here was injuries, as my top Wide Reciever and another solid Running Back both went down in recent weeks, thus weakening my team considerably. Nevertheless, I bear my team no ill will, and so I’ll let the Badgers take a bow:

  • Tom Brady: (QB) In some ways, he’s been a bit of a disappointment, but in reality, he’s done about as well as I could have ever hoped. Quarterback was a tough position to fill this year, what with all the underperforming stars and former stars and rookies and injuries. There were probably only a handful of consistent performers, and a couple of abominable weeks aside, Brady was one of them.
  • Larry Johnson: (RB) At the start of the season, there were really only 3 elite running backs to get, and LJ was one of them. I was fortunate enough to get the second overall pick in the draft, so I was able to get him (Ironically, the 3 backs were drafted in opposite order of eventual performance). Overshadowed by the obscenely dominant LaDainian Tomlinson (who has already scored a record breaking 33 touchdowns, and he still has two games left in the season), Johnson was actually my leading scorer.
  • Kevin Jones: Apparently, this guy went to my high school. Go figure. In any case, for most of the year, he was my surprisingly productive second back (surprising in that, you know, he plays for the Lions).
  • Ahman Green: (RB) He made a nice third back option when I needed him, and managed to fill in well for Jones when the injuries started coming. He spent a decent portion of the season on the bench, and I got him very late in the draft, so I was pretty happy.
  • Larry Fitzgerald: (WR) He was supposed to be my premier receiver and did very well until he got injured for several weeks. He came back towards the end of my run, and put up decent numbers. Not quite the spectacular year everyone was expecting from him, but decent nonetheless.
  • Darrell Jackson: (WR) Up until last week, he’s been one of the steadiest players on the team, consistently putting up high fantasy numbers. Then he got injured and didn’t play last week. I started one of his backups, Nate Burleson, but he didn’t do anything. Darn.
  • Jason Witten: (TE) Tight Ends don’t normally put up big numbers, and Witten was no exception. Still, i was expecting more than a single touchdown from the guy. A few years ago he damn near put up a thousand yards with 6 touchdowns (and he had a ver respectible season last year too). No one ever counts on their tight ends, really, and Witten didn’t do that bad, but still.
  • Jeff Wilkins: (K) Early in the season, this guy was putting up huge numbers. Huge. This is, of course, absurd for a kicker, and it didn’t last. Still, he did better than anyone would ever have expected.
  • San Diego: (D/ST) The SD defence was quite good this year, and netted me a fair amount of points, considering that I drafted them pretty late in the draft. I started the season with Denver, but SD consistently outscored them, so SD got the call for most of the season, and did a good job
  • Miscellaneous: I picked up Brandon Jacobs off the waiver wire and had him filling in for a few weeks during some of the injury-laden times. He makes a surprisingly decent third fantasy back because even though he doesn’t get a lot of touches, he gets them where they count: the goalline. Tiki Barber owners must be furious (this is another example of fantasy distorting reality). Kevan Barlow had a similar (but much less consistent) situation going in New Jersey, but pretty much rode the bench for me all year long. Keyshawn Johnson and Isaac Bruce both put up consistent (relatively low, but still decent) numbers and made some appearances at the flex position throughout the year, but neither really did a ton for me. I picked up Tony Romo towards the end of the season, and pretty much regretted not starting him every week (especially the week he threw for 5 touchdowns). But still, how do you start a young, unproven punk like Romo over someone like Brady?

All in all, it was a decent year, even if they did peak a little early and get injured a little too often. I’ve made it to the playoffs in two of the last three years (and the one year I didn’t was due to an uncharacteristic bad draft pick). This is actually not half bad for someone who doesn’t pay attention to sports!

Just Do It

In Paul Graham’s essay Made in USA, he writes about America’s tendencies towards design.

Americans are good at some things and bad at others. We’re good at making movies and software, and bad at making cars and cities. And I think we may be good at what we’re good at for the same reason we’re bad at what we’re bad at. We’re impatient. In America, if you want to do something, you don’t worry that it might come out badly, or upset delicate social balances, or that people might think you’re getting above yourself. If you want to do something, as Nike says, just do it.

It’s amazing how well the “Just Do It” marketing line fits America (the only other tagline that works as well is EA Sports’ “If it’s in the game, it’s in the game” line), and Graham is certainly right about how that affects programmers. I’ve noticed that there are really two different types of programmers: people who look stuff up, and people who just try it to see if it works. People ask me questions about HTML or CSS all the time. Sometimes I know the answer, sometimes I dont, but most of the time my response is “Have you tried it to see what happens?” HTML is pretty simple, and it’s easy to test out various concepts. There’s no reason not to, and I’ll also note that trying it is also the best way to learn. I’m reminded of this design parable about a ceramics class:

The ceramics teacher announced on opening day that he was dividing the class into two groups. All those on the left side of the studio, he said, would be graded solely on the quantity of work they produced, all those on the right solely on its quality. His procedure was simple: on the final day of class he would bring in his bathroom scales and weigh the work of the “quantity” group: fifty pound of pots rated an “A”, forty pounds a “B”, and so on. Those being graded on “quality”, however, needed to produce only one pot -albeit a perfect one – to get an “A”. Well, came grading time and a curious fact emerged: the works of highest quality were all produced by the group being graded for quantity. It seems that while the “quantity” group was busily churning out piles of work – and learning from their mistakes – the “quality” group had sat theorizing about perfection, and in the end had little more to show for their efforts than grandiose theories and a pile of dead clay.

There are several interesting things about this. First, as Graham notes in his essay, good craftsmanship means working fast and iterating your design. Second, failure isn’t a bad thing in this story. In fact, failure is a necessary component of success. In such a scenario, people who work fast and iterate do much better than people who meticulously plan their designs. As Graham belabors in his essay, this works for some things, not not others.

Of course, not all American designs are bad, and Graham mentions the obvious exception:

Apple is an interesting counterexample to the general American trend. If you want to buy a nice CD player, you’ll probably buy a Japanese one. But if you want to buy an MP3 player, you’ll probably buy an iPod. What happened? Why doesn’t Sony dominate MP3 players?

It’s because Apple is obsessed with good design (“Or more precisely, their CEO is.”) Interestingly, I think one of the reasons the iPod is so successful is that Apple understands the paradox of choice really well. The iPod isn’t and has never really been the leader in terms of features or functionality. But it does what it does extremely well, and I think that’s partly because the iPod is actually quite simple. If you loaded it up with all sorts of extra features, there’s no way you’d be able to keep the simplicity of the interface, and that would make it harder to use, and much less attactive.

In the end, I don’t know that I agree with everything in Graham’s essay, but his stuff is always worth reading.

Blogroll Call

Everyone loves to be on a bunch of blogrolls, but just because you’re there doesn’t mean you’ll get a lot of visitors. This becomes more true as the blogroll gets larger. Blogrolls are subject to an inverse network effect; the more blogs in the blogroll, the less valuable the link. Kaedrin gets a small amount of traffic, so even though I have a short blogroll, I’m guessing most of those blogs don’t get a ton of visitors coming from here. So I just figured I’d throw some additional links their way:

  • Transit of Mercury, Photoblogged: Jay Manifold takes some nice pics of the planet Mercury, as well as an amusing comparison of Manifold Observatory and Powell Observatory.
  • Team of Rivals: Andrew Olmsted reviews a recent book that chronicles Abraham Lincoln’s rise to the presidency, as well as the coalition he formed and maintained to fight the civil war:

    Lincoln’s ability to hold together a coalition of abolitionists, conservative Republicans, and war Democrats during the American Civil War stands as a signal feat of political dexterity that seems yet more impressive in light of more recent American history. … the book really hits its stride once Lincoln is elected and he assembles his Cabinet, beginning with his three rivals for the nomination. The contrast is particularly stark with modern politics, where Cabinets are formed from the victor’s circle of political allies. Lincoln, on the other hand, selected men who not only wanted the job he held, but who viewed him poorly at best in some cases. It’s hard to imagine a modern politician selecting men who viewed him with the kind of contempt Edwin Stanton viewed Lincoln, let alone getting the kind of results Lincoln did. Lincoln’s ability to get results from such disparate men is an impressive primer in leadership.

    Interesting stuff, and I think I’ll pick up the book at some point, as this seems to be an impressive example of compromise and tradeoffs (subjects that interest me) in action.

  • Ars Technica 2006 holiday gift guide: Make shopping for the geek in your family a little easier with this guide (sheesh, that sounded like advertising copy *shudders*). Most of the hardware and gadget gifts are pretty good, though expensive. However, they also include lots of interesting books and smaller gifts as well. Ars always has interesting articles though. I’ve already mentioned the Ars System Guide on the blog recently, but they also have reviews of the Wii and PS3 that are worth reading.
  • Casino Royale: Subtitle: Die almost never � nearly forever! Heh. Alexander Doenau’s take on the latest Bond flick is roughly in line with my own feelings, though one of these days I’ll get around to talking more about it on the blog.

    Which may beg the question of some audiences: where is the fun when there�s nary an insane scheme to be seen, and no psychedelically decorated gyrocopters? (thank you, Roald Dahl). The answer lies partly in Bond himself. Without the scary misogyny that Ian Fleming endowed Bond with 50 years ago, Daniel Craig plays Bond as an excellent bastard. This is a Bond so confident in his own skills that he doesn�t give a care who sees him because he has a licence to kill. This is probably the only Craig film we�ll see in which Bond is able to cut as loose as he did in Uganda, because part of the story involves developing a marginally more sensible and responsible MI6 agent, but he takes the sorts of risks that make the movie fun without being stupidly unbelievable.

    I love the description of James Bond as an “excellent bastard.”

  • Steven Den Beste has an interesting rating system (another subject I’ll tackle on the blog at some point). He uses a 4 star scale, but also includes a “thumbs up” or “thumbs down” graphic (for obvious reasons). This is interesting because it allows him to recognize a technical accomplishment without actually recommending the film (for instance, I would give Grave of the Fireflies **** with a thumbs down because it is masterfully produced, but so heartbreaking that I can’t actually recommend it). In any case, if you scroll down on the link above (no permalinks there), you’ll see that Steven has started rating individual anime episodes for a series called Kamichu. For episode 6, he rated it zero stars with six thumbs down. I wonder if he liked it?
  • A collection of Jonathan Swift’s journalistic texts: Ralf Goergens over at Chicago Boyz makes an Jonathan Swift-related annotation to Neal Stephenson’s Baroque Cycle:

    Attentive readers of Neal Stephenson’s Baroque Cycle will remember Daniel Waterhouse reading a a number of astonishingly vile newspapers. Some of the most acrimonious articles were from Jonathan Swift, writing for Tory papers. Stephenson didn’t make that part up, the articles can be found here.

    I didn’t have time to do more than a bit of browsing, but some of the historical characters from the Baroque Cycle are mentioned, like Marlborough, Bolingbroke, Harley and of course Queen Anne. There also are extensive footnotes explaining the concrete circumstances under which the articles appeared.

  • Weblog Awards: Kevin Murphy notes that since he was inexplicably passed over for the Weblog Awards, he might as well add a bunch of categories and simply declare winners. Normally, this would seem like the actions of a snarky blogger, but since Kaedrin won a Koveted Kevy, I’ll say it was the result of long-standing multifaceted research project considering nearly 2 billion blogs. Also, Kevin apparently knows something I don’t: Kaedrin won the Best Blog With A Japanese Word As Its Title. Hmmm. It would be pretty funny if it actually was a Japanese word (anyone know what it means?)
  • The New Threats: John Robb continues his incisive commentary on global guerillas:

    As the debate over the value of the Iraq study group’s report rumbles on, it’s important to reflect on larger frame within which this debate is taking place. This frame, little discussed, encapsulates nature of the threat we face in Iraq and will be increasingly likely to face in the future. With Iraq, we can catch a glimpse of the new class of threat that will increasingly define our future (and given that even a glimpse is enough to stump the establishment should be a dire warning). This new class of threat is characterized by its bottoms up pattern of growth rather than the familiar competition between nation-states. It percolates upwards through catalyzed organic growth until it overwhelms our ability to respond to it.

    My general reaction to Robb’s theories is that he is usually too pessimistic and that there must be a better way to fight these global guerillas, but he always makes for interesting and worthwhile reading.

  • Depressing Anime: Fledgling Otaku’s thoughts on Grave of the Fireflies are a little harsher than my own, but I have to say that he’s justified in calling it anime for emotional masochists. Don’t miss the comment threads on that post, the follow up post, and the recent post (in which he mentions my review). Like me, the more he learns of the context, the more he says he can appreciate its value as a work of art.
  • Tax Law Is Complicated, But Is It Vague? : James Edward Maule reads about a Judge who “struck down a portion of the Patriot Act on the ground that despite amendments to the provisions they remain ‘too vague’ to be understood by ‘a person of average intelligence’ and thus are unconstitutional.” As a professor of tax law, he wonders if the Internal Revenue Code is actually vague, and asks some interesting questions:

    If everything that could not be understood by a “person of average intelligence” were to be declared unconstitutional and removed from the planet, what would remain? Is there something wrong when a patient cannot understand a medical procedure used by a surgeon? Is there something wrong when a driver does not understand the engineering formulae used in designing the bridge over which the vehicle is crossing? Is there something wrong when someone enjoying a fine meal cannot understand the recipe?

  • Take my advice, or I�ll spank you without pants.: Johno over at the The Ministry of Minor Perfidy takes note of the glorious Chingrish of actual English Subtitles used in films made in Hong Kong. Some of my favorites:

    9. Quiet or I’ll blow your throat up.

    11. I�ll fire aimlessly if you don�t come out!

    18. How can you use my intestines as a gift?

    18. How can you use my intestines as a gift?

    19. This will be of fine service for you, you bag of the scum. I am sure you will not mind that I remove your manhoods and leave them out on the dessert flour for your aunts to eat. [sic, of course]

    20. Yah-hah, evil spider woman! I have captured you by the short rabbits and can now deliver you violently to your gynecologist for a thorough examination.

    21. Greetings, large black person. Let us not forget to form a team up together and go into the country to inflict the pain of our karate feets on some ass of the giant lizard person.

    This sort of thing is funny, but bad translations are also responsible for ruining a lot of decent foreign movies.

  • Extremely Cool: Indeed it is:

    The Antikythera Mechanism is a 2000-year-old device, somewhat resembling a clock, found in 1902 by sponge divers in the waters off a Greek island. It has long been believed that it was a form of analog computer, used for astronomical calculations, but its precise operating mechanism was not well-understood.

    Interesting stuff.

  • Not the intended market, but still fun: Fritz Schranck has been sucked into What Not To Wear (one of those smug reality shows that berate people for having bad style, then attempt to help them out). While I’ve never seen this show, similar reality shows do have that sorta “I can’t look away from this trainwreck” quality that makes them entertaining.
  • DM of the Rings: In terms of link love, I’ve been woefully neglectful of Shamus’s brilliant DM of the Rings comic, which somehow manages to be both humorous and insightful (well, in terms of RPG gaming anyway). Using screenshots from the movies, it’s essentially what the Lord of the Rings would have been like if it were played as a D&D game.

Holy crap, that took a while. I just realized that I would have probably been better off if I’d just done one or two a day. That way I’d have had posts every day for at least a week! In any case, stay tuned for the weekly Animation Marathon review (This week, it’s Akira. Review should be up Tuesday or Wednesday).

The Paradox of Choice

At the UI11 Conference I attended last week, one of the keynote presentations was made by Barry Schwartz, author of The Paradox of Choice: Why More Is Less. Though he believes choice to be a good thing, his presentation focused more on the negative aspects of offering too many choices. He walks through a number of examples that illustrate the problems with our “official syllogism” which is:

  • More freedom means more welfare
  • More choice means more freedom
  • Therefore, more choice means more welfare

In the United States, we have operated as if this syllogism is unambigiously true, and as a result, we’re deluged with choices. Just take a look at a relatively small supermarket: there are 285 cookies, 75 iced teas, 275 cereals, 40 toothpastes, 230 soups, and 175 salad dressings (not including 12 extra virgin olive oils and 18 vinegars which could be combined to make hundreds of vinaigrettes) to choose from (and this was supposedly a smaller supermarket). At your typical Circuit City, the sheer breadth of stereo components allows you to create any one of 6.5 million possible stereo systems. And this applies all throughout our lives, extending even to working, marriage, and whether or not to have children. In the past, these things weren’t much of a question. Today, everything is a choice. [thanks to Jesper R�nn-Jensen for his notes on Schwartz’s talk – it’s even got pictures!]

So how do we react to all these choices? Luke Wroblewski provides an excellent summary, which I will partly steal (because, hey, he’s stealing from Schwartz after all):

  • Paralysis: When faced with so many choices, people are often overwhelmed and put off the decision. I often find myself in such a situation: Oh, I don’t have time to evaluate all of these options, I’ll just do it tomorrow. But, of course, tomorrow is usually not so different than today, so you see a lot of procrastination.
  • Decision Quality: Of course, you can’t procrastinate forever, so when forced to make a decision, people will often use simple heuristics to evaluate the field of options. In retail, this often boils down to evaluation based mostly on Brand and Price. I also read a recent paper on feature fatigue (full article not available, but the abstract is there) that fits nicely here.

    In fields where there are many competing products, you see a lot of feature bloat. Loading a product with all sorts of bells and whistles will differentiate that product and often increase initial sales. However, all of these additional capabilities come at the expense of usability. What’s more, even when people know this, they still choose high-feature models. The only thing that really helps is when someone actually uses a product for a certain amount of time, at which point they realize that they either don’t use the extra features or that the tradeoffs in terms of usability make the additional capabilities considerably less attractive. Part of the problem is perhaps that usability is an intangible and somewhat subjective attribute of a product. Intellectually, everyone knows that it is important, but when it comes down to decision-time, most people base their decisions on something that is more easily measured, like number of features, brand, or price. This is also part of why focus groups are so bad at measuring usability. I’ve been to a number of focus groups that start with a series of exercises in front of a computer, then end with a roundtable discussion about their experiences. Usually, the discussion was completely at odds with what the people actually did when in front of the computer. Watch what they do, not what they say…

  • Decision Satisfaction: When presented with a lot of choices, people may actually do better for themselves, yet they often feel worse due to regret or anticipated regret. Because people resort to simplifying their decision making process, and because they know they’re simplifying, they might also wonder if one or more of the options they cut was actually better than what they chose. A little while ago, I bought a new cell phone. I actually did a fair amount of work evaluating the options, and I ended up going with a low-end no-frills phone… and instantly regretted it. Of course, the phone itself wasn’t that bad (and for all I know, it was better than the other phones I passesd over), but I regret dismissing some of the other options, such as the camera (how many times over the past two years have I wanted to take a picture and thought Hey, if I had a camera on my phone I could have taken that picture!)
  • Escalation of expectations: When we have so many choices and we do so much work evaluating all the options, we begin to expect more. When things were worse (i.e. when there were less choices), it was much easier to exceed expectations. In the cell phone example above, part of the regret was no doubt fueled by the fact that I spent a lot of time figuring out which phone to get.
  • Maximizer Impact: There are some people who always want to have the best, and the problems inherent in too many choices hit these people the hardest.
  • Leakage: The conditions present when you’re making a decision exert influence long after the decision has actually been made, contributing to the dissatisfaction (i.e. regret, anticipated regret) and escalation of expectations outlined above.

As I was watching this presentation, I couldn’t help but think of various examples in my own life that illustrated some of the issues. There was the cell phone choice which turned out badly, but I also thought about things I had chosen that had come out well. For example, about a year ago, I bought an iPod, and I’ve been extremely happy with it (even though it’s not perfect), despite the fact that there were many options which I considered. Why didn’t the process of evaluating all the options evoke a feeling of regret? Because my initial impulse was to purchase the iPod, and I looked at the other options simply out of curiosity. I also had the opportunity to try out some of the players, and that experience helped enormously. And finally, the one feature that had given me pause was video (which wasn’t available on the iPod when I started looking around). The Cowon iAudio X5 was giving me pause because it had video capabilities and the iPod at the time didn’t. As it turned out, about a week later the Video iPod was released and made my decision very easy. I got that and haven’t looked back since. The funny thing is that since I’ve gotten that iPod, I haven’t used the video feature for anything useful. Not even once.

Another example is my old PC which has recently kicked the bucket. I actually assembled that PC from a bunch of parts, rather than going through a mainstream company like Dell, and the number of components available would probably make the Circuit City stereo example I gave earlier look tiny by comparison. Interestingly, this diversity of choices for PCs is often credited as part of the reason PCs overtook Macs:

Back in the early days of Macintoshes, Apple engineers would reportedly get into arguments with Steve Jobs about creating ports to allow people to add RAM to their Macs. The engineers thought it would be a good idea; Jobs said no, because he didn’t want anyone opening up a Mac. He’d rather they just throw out their Mac when they needed new RAM, and buy a new one.

Of course, we know who won this battle. The “Wintel” PC won: The computer that let anyone throw in a new component, new RAM, or a new peripheral when they wanted their computer to do something new. Okay, Mac fans, I know, I know: PCs also “won” unfairly because Bill Gates abused his monopoly with Windows. Fair enough.

But the fact is, as Hill notes, PCs never aimed at being perfect, pristine boxes like Macintoshes. They settled for being “good enough” — under the assumption that it was up to the users to tweak or adjust the PC if they needed it to do something else.

But as Schwartz would note, the amount of choices in assembling your own computer can be stifling. This is why computer and software companies like Microsoft, Dell, and Apple (yes, even Apple) insist on mediating the user’s experience with their hardware by limiting access (i.e. by limiting choice). This turns out to be not so bad, because the number of things to consider really is staggering. So why was I so happy with my computer? Because I really didn’t make many of the decisions – I simply went over to Ars Technica’s System Guide and used their recommendations. When it comes time to build my next computer, what do you think I’m going to do? Indeed, Ars is currently compiling recommendations for their October system guide, due out sometime this week. My new computer will most likely be based off of their “Hot Rod” box. (Linux presents some interesting issues in this context as well, though I think I’ll save that for another post.)

So what are the lessons here? One of the big ones is to separate the analysis from the choice by getting recommendations from someone else (see the Ars Technica example above). In the market for a digital camera? Call a friend (preferably one who is into photography) and ask them what to get. Another thing that strikes me is that just knowing about this can help you overcome it to a degree. Try to keep your expectations in check, and you might open up some room for pleasant surprises (doing this is suprisingly effective with movies). If possible, try using the product first (borrow a friend’s, use a rental, etc…). Don’t try to maximize the results so much; settle for things that are good enough (this is what Schwartz calls satisficing).

Without choices, life is miserable. When options are added, welfare is increased. Choice is a good thing. But too much choice causes the curve to level out and eventually start moving in the other direction. It becomes a matter of tradeoffs. Regular readers of this blog know what’s coming: We don’t so much solve problems as we trade one set of problems for another, in the hopes that the new set of problems is more favorable than the old. So where is the sweet spot? That’s probably a topic for another post, but my initial thoughts are that it would depend heavily on what you’re doing and the context in which you’re doing it. Also, if you were to take a wider view of things, there’s something to be said for maximizing options and then narrowing the field (a la the free market). Still, the concept of choice as a double edged sword should not be all that surprising… after all, freedom isn’t easy. Just ask Spider Man.

Link Dump

I’ve been quite busy lately so once again it’s time to unleash the chain-smoking monkey research squad and share the results:

  • The Truth About Overselling!: Ever wonder how web hosting companies can offer obscene amounts of storage and bandwidth these days? It turns out that these web hosting companies are offering more than they actually have. Josh Jones of Dreamhost explains why this practice is popular and how they can get away with it (short answer – most people emphatically don’t use or need that much bandwidth).
  • Utterly fascinating pseudo-mystery on Metafilter. Someone got curious about a strange flash advertisement, and a whole slew of people started investigating, analyzing the flash file, plotting stuff on a map, etc… Reminded me a little of that whole Publius Enigma thing [via Chizumatic].
  • Weak security in our daily lives: “Right now, I am going to give you a sequence of minimal length that, when you enter it into a car’s numeric keypad, is guaranteed to unlock the doors of said car. It is exactly 3129 keypresses long, which should take you around 20 minutes to go through.” [via Schneier]
  • America’s Most Fonted: The 7 Worst Fonts: Fonts aren’t usually a topic of discussion here, but I thought it was funny that the Kaedrin logo (see upper left hand side of this page) uses the #7 worst font. But it’s only the logo and that’s ok… right? RIGHT?
  • Architecture is another topic rarely discussed here, but I thought that the new trend of secret rooms was interesting. [via Kottke]

That’s all for now. Things appear to be slowing down, so that will hopefully mean more time for blogging (i.e. less link dumpy type posts).

Gather Intelligence to Be Effective in Interviews, Bounty Hunting

Through following a trail of links long enough that I don’t remember where I started, I stumbled upon a post about interviewing. In itself, this is unremarkable. However, at the time, I happened to be watching an episode of Firefly (well, I had it on in the background). Because I am a nerd, I also had the commentary track on, and just as I read about the interviewing anecdote, Joss Whedon (writer/creator of Firefly) began relating something that eerily paralleled the interviewing “secret” in the post referenced above.

The “secret” is to know those who are interviewing you, and tailor your answers to match the type of response the person is looking for. He tells the story of how he interviewed for a principalship at a school in his district, or rather, how a friend helped him prepare:

She drew a rectangle on a piece of paper. “This is the table,” she said. She began to draw small circles around the table — 10 of them. She named each circle. She identified them as the people who would be interviewing me. This was not secret information, this was the panel that every potential principal had to face. The SECRET came next. She pointed to the first circle, “This is John Williams (not his real name). John tends to ask many data related questions. He likes brevity. Keep your answers short to him. Make your point and be quiet.” She pointed to the next circle. “This is Mary Thomas, she’s very child-oriented. She’s very warm and friendly and loves to talk. Answer her questions and orient your answers to how children are affected. Talk a lot with her; elaborate all your points. She’s warm and fuzzy, so use many personal anecdotes.” She continued around the table and when finished, it was like I had the playbook of an opposing football team. I knew the type of questions they would ask. I learned the type of answer each interviewer liked to hear.

This is interesting and, naturally, the advice is not limited to interviewing. (Those that have not seen Firefly but want to might want to bug out here, as Spoilers are ahead). Take Jubal Early. He’s a bounty hunter, and he’s after one of the people on Serenity. To get to her, he has to make sure the rest of the crew does not get in his way. So before he starts, he listens in on some conversations on the ship, gathering intelligence. As Whedon notes in the commentary:

Early has a very specific way of dealing with every character on the ship. He has listened to their conversation, so he understands he knows enough about them. And he understands that when you’re with Mal, you have to take him out instantly because Mal is a physical threat that is very real. And then, you know, he closes up Jayne and Zoe and all the threats … Kaylee is someone he approaches a different way – through a very horrible form of sexual intimidation. … Later on we’ll see him dealing with Book. And we’ll see him dealing with Simon. When he deals with Book, again this guy has to be taken out. which gives us a little insight into Book’s character. … And of course, he deals with Simon with logic, because he realizes that the best way to deal with Simon is to use logic because that’s the kind of person he is.

For those who haven’t seen the series, some of this might not make sense, but each approach does fit its target. Mal is the captain and he won’t stand for an outsider’s shenanigans, especially when that outsider threatens the crew. Jayne and Zoe are also physical threats. Kaylee is like a delightful pixie, which makes Early’s approach particularly disturbing. Shepherd Book is a priest, though events like the one in this episode indicate that Book has a less than saintly past. Simon is a doctor, and he’s very proper, so a logical approach fits him well.

Again, this advice isn’t limited to interviewing and bounty hunting. Knowing who you’re dealing with is important, and allows you to orient your responses to their expectations. A little while ago, I was promoted to a management position. One of the interesting changes for me is that I’m dealing with a much wider variety of people, and thus I have to modulate my message depending on who I’m talking to. Of course knowing this and doing this are two different things, and I’m certainly no expert when it comes to this stuff. It comes naturally to some people, but not especially to me.

Anyway, not something I expected to write, but the coincidece struck me…