malvasia bianca

I’m tempted to start filling this blog with complaints about recent customer experiences I’ve had, but on reflection I will avoid doing so. I am grateful to the nice person from KitchenAid customer support who spent a good half hour going out of her way to try to sort out an issue I’m having; the flip side of today’s lunch break is that whoever designed AT&T phone support is sadistic or insane.

I read a book on neuro-linguistic programming recently. It’s basically a way to reprogram your brain (e.g. to strengthen motivations or weaken phobias), using techniques like visualizing the trigger in question, then changing the way you visualize the scene. (Moving the trigger object farther away from you or closer to you, adding colors, adding theme music, …)

Which I was strangely taken by, but I have to admit that it sounds more like snake oil than not. At least I hope that the psychological profession is sensible enough to pick up on techniques that can cure serious phobias in five minutes, if those techniques actually work! Then again, it’s not like I actually took the few minutes to go through any of the exercises in the book; maybe traditional psychologists took the same approach to the ideas as I did…

Having said that, there were a couple of ideas in the book that seemed worthwhile. One was the notion of the direction of motivation: you can either be motivated towards something you want or away from something you don’t want. Or, of course, a mixture of both, even in a single situation, and certainly people can be motivated towards something in one aspect of their lives and motivated away from something in other aspects of their lives. But their claim that most people, in general, lean in one direction or the other sounds plausible to me; and I think it’s worth playing around with the idea of exploring both sorts of motivations in various context. (Of course, I still think it pales in comparison to the power of the distinction between intrinsic motivation and extrinsic motivation.)

In particular, I’m starting to buy into the notion of how powerful having a strong vision of a future goal can be. This is, of course, the core of “motivation towards”, and also ties in with their approaches that I outlined in the first paragraph. Thinking back on my life, or even about my present-day life, I think it’s not too implausible to think that the areas where I’ve been successful are areas that I’ve had a strong vision pulling me forward, while areas where I’ve been less successful are ones where that hasn’t been the case.

For example, I think you could make a reasonable claim that part of the reason I left academia was that I didn’t transform my vision of somebody who knew a lot of mathematics into a vision of somebody who discovered a lot of mathematics. I was quite good at the former and mediocre at the latter; some of that is doubtless due to my innate talents, but I bet a lot of the reason why I would pull out a math book at a moment’s notice (and work through all of the exercises in it) during parts of my life without putting in the same energy towards discovering new math later in my life had to do with my lack of vision of what the latter would be like.

Though, of course, having a strong vision by itself isn’t good enough. On that note, I thought their presentation of research on what factors lead to successful rehabilitation for injured athletes was quite interesting. The list they presented was:

1. Inner Motivation. Both towards a future vision and away from the painful present, in the case of rehabilitation.
2. High Standards. The successful athletes wanted to get back to their former peak performance levels or better: they wanted to run like the wind, not just get to where they can walk.
3. Chunking Down Goals. They broke goals into extremely small chunks, e.g. gaining an extra quarter-inch of range of motion in their feet.
4. Combining Present and Future Time Frames. They concentrated on the present when moving towards those small goals, while also having a vision of the future to sustain them through the rough times.
5. Personal Involvement. They helped design their recovery plans and carry them out themselves, not just putting themselves in others’ hands.
6. Self-to-Self Comparisons. They’re not worried about comparing themselves (especially in their injured state!) to other athletes: they’re comparing themselves today to themselves last week, and noting how they’ve progressed.

There are several things that I like about this. For one thing, it fits well with my view of areas when I’ve been successful: in those situations, I have a vision for what I want, I break that down in small steps, I take charge of my own plans, I don’t worry particularly about comparing myself against others but instead note the progress that I’ve made on my own. Whereas in areas where I don’t satisfy those criteria (which is also frequently the case), I make much less progress.

To take a much more modest example than a world-class athlete recovering from injury, I want to become a fluent reader and speaker of Japanese. That’s my motivation, mostly towards, though there’s a bit of an away from motivation in that there are art works I can’t really access right now! I won’t claim that my standards are wonderfully high, since even if I succeed fabulously there will still be more than a hundred million people who are more fluent in the language than I am, but I’m also rejecting goals of being able to just get by: one of my goals right now is to memorize the two thousand basic kanji and all of their common readings and meanings, for example, and I have no intention of stopping when I get there. But that goal will take me years to reach; that’s okay, as long as I know 14 more kanji this week than I did last week, and can keep that up for a little over two more years, I’ll make it to that goal. (I suppose that will also serve as an example of combining time frames!) I’m certainly involved personally: I’m not depending on anybody else laying out a course of study for me, I’m doing the best I can of finding resources to help me wherever I can and combining them to make a coherent plan that I’ll actually be able to carry out. And I’m not comparing myself to anybody else while doing this; sure, the kindergartener two houses down is probably learning Japanese much more quickly than I am, but that’s her, I’m me.

And, of course, I’m always gratified to see somebody talk about the virtues of breaking large tasks into small steps. I’ve certainly spent enough time obsessing about that over the last five years, whether in the TDD cycle, in breaking up features into small, coherent stories, or in the GTD notion of “next action”. It’s a very powerful concept.

The list also sheds an interesting light on Seth Godin’s The Dip. I blogged before about my mixed feeling towards the book: I initially found it seductive, but when I thought about it more it didn’t really feel right to me. And comparing it to the above list is useful: Godin does great on the High Standards part, and okay on the Inner Motivation part. (Though even there I think the fit is a bit uneasy.) I think he’s fine on the next three factors (they’re not particularly the focus of his book, but that’s okay), but the Self-to-Self Comparisons seems to me where his presentation really doesn’t work with me. Don’t worry about being better than everybody else in your niche: follow your nose, and see if you’re getting closer to your vision every day. Maybe this will lead you to being king of your niche, maybe you’ll open up a glorious blue ocean, maybe you’ll just end up having your life quietly spiritually richer without being able to say you’re more successful than your neighbors. Any of these seems like a good outcome to me; focusing on being the best has its virtues to the extent that it encourages you to set High Standards, but is harmful to the extent that you’re excessively comparing yourself against others.

Hmm, maybe I should figure out what, if any, my vision is for this blog?

I spent the day at this month’s Bay Area Go Players Association tournament. It was my first tournament in recent memory playing as a 1 dan; I had a record of 1 win and 3 losses and got the impression that 1 dan is a more accurate rating for me than 1 kyu, but that I’m not a particularly strong 1 dan.

In my first game, I took one stone, and the only reason why it was particularly close was that my opponent made a stupid mistake in the endgame that cost him about 10 points; I should have resigned earlier. Judging from conversations I overheard, I got the impression that he normally plays as 3 dan but his rating has slipped recently; I’m quite willing to believe that, it felt like he was 2-3 stones stronger than me.

My second game was frustrating in that the score on the board was 61 to 54, and the AGA rules have a rather large komi of 7.5. Oops.

The way my third game ended was instructional. We were fighting a ko; I made a ko threat. At least I thought it was a ko threat: my opponent started looking at it, and I realized that, because of a snapback, it wasn’t actually a threat to capture the stone it seemed to be threatening.

And then I looked more closely at the ko, and got really nervous. If I’d given in and connected, it would have only cost me a point. If he won the ko, rather than connecting, he’d capture four of my stones, which could be a big amount at some points in the endgame, but I had (despite my misreading of this one) several ko threats on the board that were bigger than that.

But then I realized that his capturing those four stones wasn’t all that was going on: it created a serious threat on my group adjacent to them, and in fact I wasn’t completely sure that my group would survive if I tenukied. (Which I would have to do to make good on any ko threat I would play.) This is something I hadn’t really thought of when doing ko fights: it’s not enough to just calculate the value of your opponent’s first move if he ignores your ko threat, you also have to figure out if that move is sente. And, if it is, you have to play ko threats that are enough larger to make it worthwhile to ignore that sente move.

Despite all of that, it turned out well. My ko threat wasn’t a threat in the way I thought it was; fortunately, when I read it more carefully, there was a more subtle shortage of liberties there. Which my opponent missed, so he won the ko; he captured four of my stones, lost twenty of his, and didn’t manage to capture the other ten of mine that were threatened! (In our post-game review, we decided that the best play after his initial capture lead to my group living in seki, but as it was it lived outright.) A very odd result: we both misread my ko threat, and the result was that, as an outcome of a ko fight that I’d initially miscalculated as small, the game turned from a close game to one where he resigned!

My fourth game was really weird. My opponent’s grasp of large-scale structures was even worse than mine, but he constantly wanted to get into fights with me. And, in doing so, he left himself weak, so I was constantly attacking him! Really bloody, and we both misread situations in significant ways; I misread more than he did, and lost. I really shouldn’t have misread some of those situations; the flip side is that I should probably look for clever attacks more often, because if he can find weaknesses like that in my positions, I’m probably missing some in my opponents’ positions.

One big takeaway from my first two games, which jives with my memories from other recent tournaments: I’m probably doing a better job of building up influence than I did a few years ago, but I’m also being far too cavalier about letting my opponents getting significant territory on the sides. In particular, I really underestimate how valuable it is to have an entire side of the board.

The nice non-go-related aspect of the tournament was that it was in the SF Japantown. I had lunch at Sapporo-ya, which doesn’t look like much from the outside but which we discovered has quite good ramen when we tried it out because we NEEDED FOOD NOW the last time we went to Japantown. And I did some shopping at Kinokuniya; they didn’t have what I was looking for (more Puzzle Nikoli books; fortunately, the ones I have will last me through the only upcoming trip we have planned), but I found a go book I didn’t already own.

And I browsed through the instructional language section, and acquired more inventory there. Which doesn’t entirely thrill me, but I’ll be finishing my Japanese textbook in about half a year, I’m not sure I’ll go to a Japanese bookstore between now and then, and I could use ideas from browsing in a bookstore. And if I learn about books that I want to buy while browsing in a bookstore, I’m going to almost always buy them there, instead of noting them down and buying them elsewhere. The haul:

• Collections of essays and fiction with “translations of all the complex passages”, copious notes, and a dictionary. (And a CD and profiles of the authors.) I’m really excited about these: they look like a great way to make the transition from book learning to reading real Japanese.
• Two volumes of Japanese in MangaLand: I liked the other introduction-to-Japanese-via-manga book that I read, so I figured I’d give these a try as well.
• A Dictionary of Basic Japanese Grammar. I bought this partly because I figure it might be a reasonable thing to read once I’m done with the textbook and/or a reasonable reference, but mostly because there’s an intermediate grammar in the same series, which I expect will be a good follow-up to the textbook.

All in all, if I’m going to accumulate inventory, it doesn’t look like too bad a choice: I have specific triggers coming up in the not-too-distant future that I expect will cause me to start reading all of them, and I’ll probably start reading the manga volumes sooner than that: the first one would be a good candidate to bring on vacation.

A quite pleasant day. I even got some studying done over lunch, so I didn’t particularly fall behind in my regular activities.

In response to a tweet and tumblr post from Brian Marick:

According to the speaker in a talk I went to several years ago, it was the case until some time last century that educated Chinese people would have memorized hundreds of books going back as far as thousands of years. And these books wove together in a thicket of references: when an author wrote a phrase, it wouldn’t just be an allusion to a phrase/incident in a single book X. Instead, it would be an allusion to a phrase in book A written two thousand years ago and also to phrases is books B, C, D, and E that were written over the intervening centuries/millennia that all also alluded back to book A.

Rock Band arrived today. Despite her lobbying for Mario Kart Wii as our next game purchase, Miranda was plenty excited to see it show up; she helped me carry it in from the car (which was actually pretty useful, the Amazon packaging makes it just bulky enough to be very awkward to carry by yourself), and she had it mostly unpacked by the time I was done studying Japanese.

So we tried out the quick play multiplayer mode. I was on guitar; at first, she wanted to play the drums, but she found it kind of frustrating, and switched over to vocals after a few tries. I was worried that vocals would be kind of tricky since she’d never heard the songs before (which makes a difference on vocals since, unlike the other instruments, you’re not just responding to straightforward cues, you have to know something about the melody of the song), but she did fine, making it through all four of the the introductory songs.

While we were heating up leftovers for dinner, I downloaded Still Alive; Miranda was twice as excited when we saw that. I read the manual during dinner and figured out how we could make characters, so she didn’t have to play as (horrors) a boy (incidentally, I was very disappointed at the lack of beards; googling, I guess I’ll be able to unlock that?); we then played through Still Alive a few times. You could tell that she had practice with the song: on her first try (on Easy), she got it 100% correct, we were still doing fine with me on Expert and her on Hard, and I’m sure she would have done well on Expert as well. (It didn’t hurt, of course, that it’s a pretty easy song, at least compared to my memory of songs in the original Guitar Hero. Though I was surprised to see Expert having you switch between green and orange buttons so quickly; I didn’t remember that before.)

Quite a pleasant evening. I’m not thrilled with the guitar, but it’s okay, and Guitar Hero III should show up tomorrow and fix that problem. I’m curious to give the drums (and, for that matter, the vocals) a try. And I hope we’ll convince Liesl to join our band soon…

Any recommendations for other songs to download? I’m sure we’ll be happy for quite some time playing the songs on the disc, but, with that game, it would be a shame to not explore the downloadable content.

Jordan: I don’t suppose you’re ready to give in and get an Xbox 360, are you?

Warning: it is entirely possible that none of my regular blog readers will care about this in the slightest. I’m only writing it in case some other random person out there is dealing with this problem and googles for a solution. In particular, if the next paragraph makes your eyes glaze over, just move on, there’s nothing to see here.

Make has a feature called ‘vpath’. You can use this to tell make to look for your source files in some other directory or directories. We use this at work because, in a few circumstances, source files for one program/library/whatever can be taken from multiple other directories; that may sound like a bad idea to you, and I won’t argue with you, but I also don’t have the energy to eliminate all situations where we do that. And vpath deals with that situation just fine.

Except when it doesn’t. Sometimes, bad things happen for obvious reasons (e.g. identically named files in two different source directories); that’s easy enough to fix. And sometimes, as happened last week, bad things happen for really screwy reasons: like you move a source file, but a mention of the old location occurs in an automatically generated dependency file; that in of itself wouldn’t be a big deal, I know how to write dependency files in such a way as to be able to handle that (yay, gcc -MD -MP), but occasionally make’s vpath machinery can get really fixated on the old location.

And the screwy thing is, when we specify the source files, we specify the directories that they’re located in; it’s just hard to write wildcard rules to handle that without throwing away information and using vpath!

Well, it’s actually not that hard, it turns out. Here’s a sample Makefile using vpath:


all: foo

clean:
    -rm -f *.y foo


Try it out yourself: just create directories a and b, and files a.x and b.x in the corresponding directories. Notice how all the information is there in SOURCES; but then we strip it away to get the %.y: %.x rule to work. Which is screwy.

Here’s how you can avoid it:


all: foo

clean:
    -rm -f *.y foo


(Your web browser is probably wrapping the foreach bit over two or three lines, don’t be confused.)

Which is quite simple, as it turns out. (At least once you realize recent GNU Make versions have eval.)

Some warnings:

• The special variables from pattern rules (@$, @?, @*, etc.) don’t work in the eval version of the rule, so make sure you write the rule directly in terms of its arguments
• GNU Make 3.80 has bugs involving eval, so if you’re using that version (and it isn’t patched by your OS distro), you may want to upgrade to 3.81.

If you’re still reading by now, I, um, salute you? Glad to meet another member of the club of people-who-think-about-make-more-than-they-should…

The Gold Mine is a business novel about lean. It’s clearly inspired by The Goal; it isn’t nearly as good as the latter, but it does have some real virtues.

The Goal did, in my opinion, a remarkable job of pulling the reader along in the journey of discovery: you could really believe that the protagonist was figuring out this stuff (with Jonah’s help) as he went along, indeed you as the reader were probably figuring out some of the stuff as you went along. (Goldratt consciously adopts a presentation style designed to encourage that.) I’m a bit ashamed to admit it, but I even found the cheesy personal crisis parts of that book somewhat gripping. For some combination of those factors (and because ToC is inherently fascinating stuff), I stayed up way too late finishing that book.

The Gold Mine, in contrast, didn’t have those virtues. Honestly, I’m not sure that somebody who hadn’t already drunk the lean kool-aid would be any more likely to be interested in lean after reading this book than before.

But, as I read along, I found that it had other virtues. If you, like myself, have drunk the lean kool-aid, and if you’ve read some of the theory, you’ll find that this book fills in some gaps. By presenting a (fictional) case study of a lean transformation, it gives some practical advice on how to carry out a lean transformation that I haven’t seen elsewhere. (Not that I’ve looked a lot.) It presents an order in which to introduce the various lean concepts and techniques, it gives you some pointers about what are good and bad signs in your transformation, it makes ideas rather more concrete than I’d seen elsewhere.

I imagine that most readers will also learn something about some of the lean concepts while reading the book. I’d never thought much about 5S, for example; but it’s one of the earlier tools that they introduce in the book, and it has wider-ranging effects (psychologically as well as in its direct effects on processes) than I’d realized. Other people may already be more familiar with 5S than I was, but I suspect that most non-experts will find something new here.

It’s not the first book that I’d recommend on the subject, but I’m certainly glad I read it. It was a pleasant enough way to spend my breaks for a week or so at work, and there’s good stuff here; it’s just not what I expected before I started!

Over the last couple of years, I’ve noticed my preferences for online video game coverage shift. I’ve been following the traditional news/reviews-oriented web sites for years (over a decade in some cases), and IGN is still one of the first places I visit in my nightly web surfing. (I never dipped into the forums for those sites, though, for what that’s worth.) So, when IGN started podcasting, I subscribed.

There were things I liked about their podcasts, and things I didn’t like about them. Their podcasts are more informal, more discursive, compared to the articles on their site; listening to people chat who have spent years immersed in video games is, in general, all to the good. But there were aspects I didn’t like so much: the staff is almost entirely male, there’s occasional casual sexism and general young man chest-thumping that I don’t really have much patience for. Which is part of the reason why I stay away from video-game forums, since the problems are apparently much much worse there; that’s also the reason why I haven’t been eager to start seriously using Xbox Live.

When I started reading blogs, I subscribed to some of the larger news video game blogs. But I’ve been moving my blog reading away from them and to sources with a different flavor more recently: the news is pretty much the same on all these sites, while other sources are giving me perspectives that I’m not seeing in the big sites.

One example that I’ve been avidly reading recently is Michael Abbot’s Brainy Gamer blog. (And listening to his podcast!) He has a very pleasant style, interesting things to say, and he’ll not infrequently spend time talking about games that are years old instead of games that were published yesterday. As somebody who doesn’t have the bandwidth to play all interesting new games as soon as they come out but who has played a good number of games over the years, I very much appreciate this broader historical perspective. (And I’m apparently not the only one: on a podcast episode, he mentioned that many other older games like his site.)

Other people that come to mind: Leigh Alexander, N’Gai Croal, Stephen Totilo. Those last two were a bit of a surprise for me: I’ve basically dismissed video game coverage in mainstream sources until now, thinking that, at its best, it’s casual coverage for parents to figure out what to buy their kids and, at its (all-too-frequent) worst, it’s actively offensive. But there are some people writing in mainstream sources who love and respect the genre and have some very interesting things to say.

And I think gender issues are probably relevant to the four people I just mentioned. Only one of them is female, but the other three spend time in places (academia in one example, non-video-game-specific media in the other cases) where I imagine they work closely with women on a regular basis, unlike the gaming-only sites. Perhaps because of that, perhaps because of other reasons, their style is different from what I see in the more personal side of gaming-only sites: none of the young man posturing, none of the casual sexism (don’t get me wrong, there are a lot of places that are a lot more sexist than IGN podcasts, but it’s there and annoying), an environment where I’d much rather spend time.

(Incidentally, I have sexism more on my mind than normal right now, because a mailing list that I care about just self-destructed this weekend because it couldn’t deal healthily with discussions of sexism. Not sure I want to blog too much about that, but I wish it hadn’t happened. But I’d been thinking about this blog post for a few weeks now, so it’s not really a reaction to those events.)

So: what do I want out of a video game community? Or perhaps: what do I want out of a video game web site, what would cause me to be more of a community participant in it and less of a disengaged reader?

Here’s one way I’ve been thinking about game coverage recently: video game web sites, by and large, spend time on three different sorts of things. We can label those three things temporally:

• Coverage of forthcoming games.
• Coverage of games as they are released.
• Coverage of games that were released some time ago.

That sounds simple enough, but it turns out that these forms of coverage have a quite different nature from each other.

To start with the middle one, this basically translates into reviews of games as (sometimes slightly before) they are released. And it’s the main reason why I plan to keep on subscribing to IGN indefinitely: I like knowing something about basically every console video game that comes out, which means at least skimming the majority of their reviews, and reading the reviews for games that seem at all noteworthy, even if I’m unlikely to buy them.

The former category is the one that bothers me more and more. It must contain a good 95% of the material on most video game web sites; and I’m increasingly wondering how it does me the slightest good at all. I suppose it’s not a bad idea to be aware of important forthcoming games a little while before their release, or to have more context for them than a review can provide; but what we actually have is coverage of games that starts years before the games will actually be released (if indeed they ever get released), with the effect of building up excitement about games up until the point where they’re actually released. At that point, people may or may not play the game (most people obviously won’t play the vast majority of games), and the focus switches immediately to other upcoming games.

The result is that people (including myself) spend significantly more time learning about upcoming games than we do actually playing the games, and that we’re basically immersing ourselves in coverage that has a similar (but much much stronger) effect to advertising. I’m starting to wish that video game sites would simply stop doing advance coverage of games: just don’t talk about games until, say, a month before they’re released, or a week before they’re released, or the day that they’re released. Yes, I want to learn about games, but why wouldn’t it be better for me to learn about the actual published games themselves, instead of some fantasy of what future games might be like a year from now?

To get back to the themes from earlier in the post, I also suspect that this focus on early hype of games reinforces some of the most unpleasant aspects of video game communities. The stereotypical forum is filled with 14-year-old boys; these are people who are in the unpleasant situations of constantly having to deal with (group) identity formation and of not having a lot of spending money. Both of those have the effect that they are pushed towards picking a few games (and one console), and supporting them/it to wildly irrational and unpleasant extents; the focus on advanced hype for games just gives more grist to the mills of irrational video game loyalty.

And then there’s the third temporal category, coverage of games that were released some time ago. There’s very little of this on most sites; I have to see that as largely a consequence of the extreme focus on future potential games. And that’s another reason why I’m getting mad at the latter: I like reading people talk about games at leisure, in a reflective fashion. You get almost none of that from advance coverage, by its very nature (or rather, to the extent that there is leisure in the advance coverage, it consists of obsessively dissecting every scene of a trailer for a forthcoming game you’re excited about, because you won’t have any more information about it for months); good video game sites will provide thoughtful reviews, but the reviews are done under pressure, and don’t have the benefit of looking back on the game from the broader perspective of a few months or years (or decades).

And reviews at release time also don’t allow me to be a part of the conversation: I buy very few games at launch, and even if I do, I won’t be able to finish playing them until, at best, a month or so later. By that point, the broader discussion on the main sites has long since moved on to other things. And, to the extent that those sites do coverage of past games, it’s so often in terms of game-of-the-year discussions and the like, which is the most shallow sort of reflection. And which leaves me out in the cold, because I don’t have time to play the 10 serious GotY contenders that the industry will release in the last three month of the years.

So, to recast the three categories, what they really mean are:

• Hype building. This is by far the dominant category, it basically has the effect of being free advertising for video game manufacturers, its influence is almost entirely negative.
• Reviews of games as they are released. A useful category, present in an entirely appropriate proportion. (But unduly influenced by video game publishers, though not currently to an unacceptable extent as far as I can tell.)
• Reflection, discussion, discursion on past games; depressingly lacking in most web sites.

I’m on the lookout for web sites in which the proportion of those three categories are reversed, where the reflection happens from as many different viewpoints as possible.

The SuperMemo ideas don’t seem to be leaving my head, and I’ve finally gotten my todo backlog under control, so I think I’ll take a shot at implementing them. Some notes:

What algorithm should I use to schedule the reminders? I’ll work under the theory that each item that I want to remember is best reviewed at exponentially increasing intervals; see, for example, Wozniak’s Algorithm SM-4. (Though I should note that Algorithm SM-11, his most recent version, seems to drop this assumption.) And, of course, different items are best reviewed at different rates, depending on how easily my brain seems to remember them; let’s call the multiplication factor that we use in the exponential curve for an item its “difficulty factor”. (Where smaller DF = more frequent repetitions = more difficult.)

In SM-4, he suggests that a natural goal is to try to remember items correctly 90% of the time, and that a difficulty factor of 2.5 makes sense as a first guess. In earlier versions of the algorithm, he has what seem to me somewhat complicated ways of tweaking the difficulty factor, but, in later versions, it gets simpler: if you get it wrong, start over reviewing the item from scratch, and increase the difficulty.

Given that, assume you’ve gotten an item wrong W times, and have S winning streaks of 10 correct answers. (So a 20-win streak would count two towards S.) (Though, with the power of exponential growth, a 20-win streak would take decades at all but the hardest difficulty factors.) Then I’ll set the difficulty factor DF for that item equal to 2.5 – .1(W – S). The point here is that ten correct answers balances one mistake, which fits with getting it right 90% (or 91%, I suppose) of the time. And I pulled the .1 more or less out of my hat: I don’t want the difficulty factor to get too close to 1 most of the time, and subtracting .1 each time I get it wrong should fit in well with that goal, based on my experience over the last year with Japanese vocabulary.

With the above definitions, assume that your current winning streak for an item has length n. Then I’ll say that you review the item immediately if n=0, and review it in DF^(n-1) days if n > 0. Actually, I think I’ll change that last to (DF^(n-1)) – .5 days, since I only plan to do the review once a day, and I want to avoid weirdness that might occur if I do it at 8pm one day and at 6pm the next day, or even 11am.

This looks pretty simple: for any given item, I just have to store the next review time, W, S, and n to have enough information to schedule future reviews. (And the fact that one of the items to store is the next review time is very convenient, because that means I can figure out what to review by just doing a simple database query on that column.) I could even store W – S instead of storing both W and S, but I think I’ll keep them separate. One reason for this is that one of the ideas in the original is that different items can be considered more important to learn or less important to learn; if I have something that’s really important to learn, e.g. kana characters, then I could have each mistake count as -.2 instead of -.1, while each 10-time winning streak would still only count as +.1.

That’s the algorithm; what do I use to program the application? One of my motivations is to make it easy to continue my studies when I’m on vacation, or for that matter during my lunch break at work, so I’d like to make this a web app. It looks like a good fit for Rails, and I’d been meaning to get practice with Rails anyways, so that’s what I’ll use. Hmm, what are the best ways to learn about Rails? It’s alleged to be simple enough that I should probably just jump right in and program instead of spending hours reading about it.

The program will have to present questions and answers; each one will be a simple Unicode text field. (And I’ll want to do automatic line wrapping but to preserve manual line breaks.) It won’t affect the programming, but I’ll have to learn a bit more about multilingual input in the various operating systems I use; I’ve done kanji input on the Mac, hopefully it won’t be too hard in Linux, either, and hopefully it will be easy to switch between keyboard layouts on the fly. I can start off with buttons for “show me the answer” and “correct/incorrect”, but eventually I’ll want keystroke inputs for those, to minimize typing. And that’s all there is for the “test yourself” part of the interface; I’ll also need an interface for adding questions and for editing them. (Where the latter will require search functionality.)

If this works well for me, I may well want to let Miranda use it to help with her German; so I’ll have to think about account management, authorization, security. (And if any of my readers are curious, I’d be more than happy to open it up to y’all, too.) OpenID is the trendy up-and-coming authorization mechanism these days; maybe I’ll give that a shot? I would assume that there’s probably some Rails plugin that makes OpenID easy to use.

That should be enough to get me going; in particular, I have a clear next step, to get my hands dirty with Rails, and I have a clear first goal, to get the basics of adding and reviewing items working locally. And then followup goals of searching/editing and of doing this remotely in a not-hopelessly-insecure fashion; I’m going on vacation for a week in August, so I’ll try to get to that stage by then. The multiuser stuff can wait until after that.

Should be a pleasant way to spend some of my free time over the next few months. Andd it will directly address some of the issues I’m having with my current Japanese review: I’m currently managing to review vocabulary items both too frequently and not frequently enough! So I’d really like an algorithm that asked me questions at just the right time.

Anybody have a (landline long-distance) phone company that they like? I recently discovered that the long distance company that we’ve been using has been treating us badly (hint: grandfathering people into their plans only makes sense if their old plan is better than the plans new customers get), so we’re shopping around.

The introduction to Pimps and Ferrets: Copyright and Culture in the United States, 1831–1891, by Eric Anderson, leads off with a quote from an 1888 issue of Scientific American lamenting that

all postmasters and customs officers throughout the United States are constituted pimps and ferrets for these foreigners

in regard to a proposed copyright law. The full quote (from the May 19, 1888 issue):

The bill in substance provides that […] copyright patents shall be granted to foreigners; they may hold these monopolies for forty-two years; the assigns of foreigners may also obtain copyrights; all postmasters and customs officers throughout the United States are constituted pimps and ferrets for these foreigners; it is made the duty of postmasters to spy out and seize all books going though the mails that infringe the copyrights of foreigners; if an American citizen coming home brings with him a purchased book, it is to be seized on landing unless he can produce the written consent of the man who owns the copyright, signed by two witnesses. Who the said owner may be, in what part of the world he lives, the innocent citizen must find out as best he can, or be despoiled of his property.

I confess that I only skimmed the rest of the dissertation, but I couldn’t pass that quote up; for what it’s worth, the dissertation seemed quite readable, and I recommend it to anybody who happens to be curious about 19th century copyright in the US.

(Via Against Monopoly.)

I read Good Calories, Bad Calories about a month ago, and it’s thrown me for a bit of a loop. I’ve had reasonably high cholesterol for a while, and one of my grandfathers died from a heart attack at a younger age than I’d prefer to die, so I’ve been vaguely curious about the subject for a while. But, on the flip side, I like to eat, and there’s a lot of food out there with a high fat content that my life would be much less rich without.

So, for now, I’ve been mostly sitting on the sidelines, watching amused as the fat evidence changes over the last few years. Olive oil is now not only not bad for you but actively good for you; high-fat fish, ditto; while trans fats are now demonized as uniquely bad for you. All of which fits well with my personal preference to eat good food: I’ll take butter over margarine any day and will happily avoid processed junk food where partially hydrogenated vegetable oil is high on the list of ingredients. I was very happy with the “chocolate is good” studies, too; I’m eagerly waiting for somebody to show that cheese is similarly beneficial, though ice cream seems like a bit to much to hope for even to me.

Still, my cholesterol is high, and was a good deal higher when I got it checked a year ago than it was back in my grad school days. My doctor didn’t like that, so she put me on simvastatin; my cholesterol level responded quite nicely to that, yay.

But I perked up when I read about Taubes’s book. I’m pretty sure I read this New York Times article, which discusses Taubes’s claim that the evidence for a link between high fat consumption and heart disease is not very strong.

Which is the subject of the first part of the book; reading it, it looks to me like he’s done a pretty good job of gathering his evidence. His reasoning seems sound, his critiques of others’ reasoning seems sound. Maybe he’s misrepresenting the evidence, I’d like to see an equally well-done refutation of his points, but right now I’m not very convinced at all by the “fat is bad” claims.

What I wasn’t expecting was the rest of the book. One of Taubes’s points is that studies frequently focus on links between cholesterol and death from heart disease. And heart disease is bad, no question, but what I really want to do is increase my (enjoyable) life span, not decrease my chance of dying from heart disease while increasing my chance of dying from something else. (I also don’t want to increase my life span by two months at the cost of having to eat mediocre food for decades, but that’s a separate matter! Not an unimportant one, though.) After talking about fat, he turns to a range of other diseases (diabetes being the one that stuck in my head the most) that, apparently, are completely unknown in many populations before they start moving towards more western lifestyles. (And not unknown solely because of lower life expectancies, either.) So there really is reason to believe that dietary changes over the last century have had significant negative impact on our health; fat, however, doesn’t seem to be the smoking gun.

With which he turns towards presenting a case against excessive carbohydrate consumption. I’d assumed that the Atkins diet was just another fad diet; apparently, it has a rather long history, and the science behind it is a good deal more interesting than I’d thought. (Including links between it and some of the bad kinds of cholesterol; I’ll pay more attention to my triglyceride levels in the future.)

I’m not completely convinced by either the “fat is ok” or “carbohydrates are bad” parts of his argument. (And I don’t think he expects readers to be; the impression that I got is that he’d like a lot more research in certain areas and a lot less reflexive going along with the crowd.) But this doesn’t mesh too badly with my experience; in particular, one of the big changes in my diet since moving out here is that (partly because of the best cookbook ever), we eat pasta all the freaking time. And, going back to my “eat good food” mantra from above, I have a hard time supporting the notion that our diet isn’t rather too pasta-heavy; I’m sure Italians would look at our family menus with horror. So it does seem time to reconsider that part of our diet. And also to ask some basic questions: I’d never seriously considered eating brown rice or whole-grain pasta; maybe I should try them out and figure out if I like them? (The answer turns out to be that I actually seem to prefer brown rice in most contexts; I’m not completely sold on whole-grain pasta yet.)

So we’re experimenting, and our meals have gotten more varied. I’ve done some googling to try to figure out if Taubes is a crackpot or not; so far, I’m not seeing much reason to reject him. Take, for example, this article on carbohydrates from the Harvard School of Public Health. In one section, it talks about measuring the effects of different diets, including the Atkins diet, and says “it looked as though the women in the Atkins group had lost the most weight … and 3.5 for the Zone group. (18) Levels of harmful LDL, protective HDL, and other blood lipids were at least as good among women on the Atkins diet as among those on the low-fat diet”. Note the use of “looked as”: already, we see a rhetorical anti-Atkins positioning in an attempt to mute what sure sounds like good news for Atkins.

They justify their skepticism by saying “If you read the fine print of the study, though, it turns out that few of the women actually stuck with their assigned diets. Those on the Atkins diet were supposed to limit their carbohydrate intake to 50 grams a day, but they took in almost triple that amount. The Ornish dieters were supposed to limit their fat intake to under 10 percent of their daily calories, but they got about 30 percent from fat. There were similar deviations for the Zone and LEARN groups. What this and other diet comparisons tell us is that sticking with a diet is more important than the diet itself.” And, frankly, they should be ashamed of that conclusion: they’re trying to pretend that all of the diets would be equally effective if people stuck with them, without a shred of evidence presented in favor of that, while simultaneously brushing away what evidence the study actually presents.

This is exactly the sort of thing that Taubes mentions over and over in his book, where studies are interpreted in as anti-fat a method as possible. And there’s more of it later in the article: they admit that certain studies give evidence that certain low-carb diets are good for you, but present this in a tone of “well, if you go the low-carb route, you probably aren’t consigning yourself to early death, but who knows” rather than “you know, maybe these low-carb people really are on to something”.

If nothing else, being kicked out of a diet rut is to the good. And I’m happy to no longer have to feel guilty about eating bacon.

• Untangle, a flash game about representing graphs as planar with straight edges. (Hmm, are there planar graphs that can’t be drawn with straight edges? Not clear to me.) I linked to another game like this before, but this one’s better.
• TypeRacer, if you’re curious how fast you type. (I’m usually in the 95-100 wpm range, it seems.) (Via Game | Life.)
• Japanese anatomy scrolls from 1819.
• The Piet programming language. (Via Notional Slurry.)

• An amazing video:

  (You’ll have to bear with it a bit, it doesn’t really get going until about 40 second in.) (Via Penny Arcade)

• Japanese highway interchanges. (Via Pink Tentacle.)

• How to crush an egg:

  (Via Vacuum.)

• Pretty pictures. (Via Drawn!.)
• Virtual methods in the CLR and JVM. (Perhaps only interesting to me because I’m so ignorant about the CLR…)
• Samuel R. Delany gets laid more than I do. (Click on “The Polymath”; not even direct-linkable, alas, let alone embeddable.)
• As a manager is explaining that photography is allowed in Union Station, a security guard comes over telling them to turn off the camera…

Phoenix Wright Ace Attorney: Trials and Tribulations is the third game in the Phoenix Wright series. I don’t have a lot to add beyond what I said before: it’s a good series, and if you’ve played the other games, then by all means play this one as well, while if you haven’t, give the first game a try.

The mechanics haven’t changed at all since the second game, which is fine; there’s enough to do, and if they’d added anything more, I suspect it would have felt gimmicky. The game starts off a good deal harder than the earlier games, with very little gentleness towards newcomers; fortunately, it doesn’t get any harder after the second case, and in fact I found the last case slightly easier than some of the earlier ones. (Or maybe my brain was just getting back in the groove.)

Amusing enough new characters, but no spectacular additions. (Though the chef is quite something, for better or for worse.) They continued the story arcs set up in the first two games, bringing it all to a conclusion in the last case of this game; timeless plotting it isn’t, but it did all come together acceptably (if not wonderfully) at the end. As with the earlier games, Liesl played all the way through this one, finishing it before I did. (Partly because I was obsessing over Professor Layton.)

I’m not 100% sure that I’ll play future games in the series, now that this plot arc has come to a conclusion; if Liesl wants to, I will, otherwise who knows. (It may depend as much as anything on how many vacations I take.) But I’m quite glad I played through these three.

I was very sad to learn that Erik Ray died on May 14, after being hit by a car while riding his bicycle. He was more of a friend-of-a-friend than a direct friend, but I certainly enjoyed the time I spent with him when we were both living in the Boston area.

For those of you who come here for video-game-related reasons, he worked on the excellent System Shock in a variety of roles, including doing some of the level design. He also wrote a pleasant introduction to XML.

But the main reason why I miss him is Lambda Expressway. It’s a fabulous quirky audio novella, mixing a sort of adventure story with mentions of the virtues of building your own backhoe, a character with a theme song immortalizing the virtues of buns, and, well, just go listen. (I do every year or so.)

I think I have another tape or two of his around somewhere; I really need to go and get them digitized. I hope they haven’t fallen apart…

Liesl’s car is getting a bit long in the tooth, so a week and a half ago we went and test-drove some cars. And decided on a Prius; one of the surprises was that I actually preferred its interior dimensions to the Camry’s. (I kept bumping my head on the Camry’s ceiling.)

We didn’t like the dealer we test-drove it at enough to want to give them our money (and the only package 2 Prius they had in stock was black, which didn’t sound great for summer driving), so we sent out some inquiries via cars.com. Piercey Toyota in Milpitas got back to us saying that they had a non-black package 2 in stock for $23,909. That sounded fine, so we left them a voice mail.

And didn’t get a response—I guess the person we were dealing with was unavailable on the weekend?—but we heard back from them yesterday, and made an appointment to drop by there this evening.

So we show up; the first words are “I have some good news and some bad news”. It turns out that they don’t have one in stock any more, which was pretty annoying; couldn’t they have e-mailed us to let us know? Still, we wanted a car, so we probably would have been willing to put down a deposit or something and wait for a week for the one they had on order to show up.

But, it turns out, Toyota has raised the MSRP in the interim: not only would we have to wait a week, we’d have to pay a few hundred bucks more. They kept us sitting around for a good twenty minutes or so while thinking about whether or not they really wanted to charge us the MSRP, but ultimately they stayed firm: if we wanted a car, we’d have to pay the higher price, instead of the price they quoted to us.

Which Liesl and I were both furious at, and were completely unwilling to do. The reason why we went through cars.com in the first place is so we wouldn’t have to deal with stupid dealer crap: they’d make us their best offer, we’d take it or leave it, no hard feelings either way. Instead, they told us one thing, gave us no indication that anything had changed, had us drive through rush-hour traffic to get there on an evening when, frankly, we had better things to do, only to tell us then that they wanted to change the price on us.

I’m not particularly mad at them for selling the one they’d mentioned on the e-mail: it’s a hot market, we didn’t jump in our car to drive there and buy it immediately. (Though, you know, it would have been nice if they’d indicated that they wouldn’t hold it for us unless, say, we called them to put down a few hundred bucks as a down payment or something: we got back to them pretty quickly, after all.) But if they are going to sell it and we’ll have to wait for a week or two to get another one, it’s simple basic courtesy to spend a minute and send us an e-mail: that way, we would have known what was going on, and hopefully we could have avoided tonight’s trip entirely, arranging whatever needed to be arranged over the phone.

Even with that, though, we would have been willing to put down a deposit for the next car tonight when we showed up and were told that, in fact, they didn’t have a car for us. But to change the price like that with no advance warning is completely unacceptable. Basically, it turns out that what their original “we have a #2 Prius to sell you for $23,909” e-mail actually meant was “we’re a Toyota dealer, it’s likely the case that we’ll be able to sell you a Prius at some point in the future for some undetermined price.” Which we could have figured out quite nicely on our own without blowing an evening on it, thank you very much.

Liesl will contact the next dealer on our list tomorrow; hopefully they’ll be more honest in their dealings with us.

One thing which I was expecting to find in the GTD book, but didn’t, was some sort of version of Standardized Work. This is an idea that I’ve seen in lean: it says that, if there’s a task that you do repeatedly, you should write down the best way you know of to do that task. From then on, you should either follow your standardized work guidelines when performing that task or be consciously experimenting with a new way to perform that task. (And then, depending on the results of the experiment, either updating your standardized work or going back to the old way.)

This is, of course, not an idea that is original to lean, and, in fact, I have heard David Allen mention it (either in a podcast or in another book, I can’t remember), under the term “checklist”. But I still think its absence in the book creates a gap; here’s why.

One of his quotes in that book is “There is no reason ever to have the same thought twice, unless you like having that thought.” (p. 22) That’s perhaps a bit of an exaggeration, but it is true that GTD trains you to capture certain kinds of thoughts (worries, ideas, …) as they flit through your mind, and write them down.

So: if the thought is a next action, it goes on your next action list. If it’s related to a project, it goes on your entry for that project. If it’s something you’re thinking about but haven’t yet committed to, it goes on your someday/maybe list.

But what if it relates something that you do repeatedly? You may be able to place that in one of the above categories, but, for me, they’re not a particularly good fit. That may sound a bit abstract (or wrong!), so let me give you an example as an explanation: sometimes, I am hiring. When I hire, I bring candidates in for interviews. And setting up an interview involves several steps: the candidate and I have to agree on the time, I have to reserve a conference room, I have to register the candidate with the visitor system, I have to make an entry in my calendar, I have to e-mail the candidate driving directions. And probably other steps that I can’t think of right now, which is exactly my point: I can try to hope that I’ll remember all of those steps, but they’re exactly the sort of thing that GTD teaches us not to keep in our brains, to keep instead in some trusted location.

But where? If I’m hiring, I’ll have a ‘hiring’ project, so I could keep it there. If I’m not hiring, I guess I could shuffle it over to the someday/maybe list. But that sounds like a lot of busywork for no particular reason; instead, I find it simplest to have a ‘checklist’ folder where I keep stuff like that. (If you’re curious, the GTD directory on my computer contains my tickler file plus four subdirectories: ‘projects’, ‘someday’, ‘reference’, and ‘checklists’.) So, at work, this is more or less my current set of checklists: a couple of hiring-related ones, one for when somebody leaves, one giving the steps of my weekly review, and my favorite ones, the checklists for when I get to work and leave work. (I created the “get to work” checklist the second time that I realized that it was almost lunchtime, that I’d been too busy to eat breakfast at home, and that I’d gotten distracted and hadn’t eaten breakfast at work; so I created a checklist whose fifth item is “have I eaten breakfast?”.)

Incidentally, my GTD system is settling down pretty well. I’ve made peace with the e-mail sorting issues that I mentioned earlier; once I’d added short keystroke commands to file an e-mail as action/waiting/scheduled (along with keystrokes for various reference folders), I found that having separate folders for those categories worked fine. I’ve instituted weekly reviews at both home and work; they haven’t had any big effects yet, but seem to be a positive occurrence as a whole. My personal next action list has been getting out of hand recently, but I made some progress in taming that this weekend, and it’s been a successful feedback mechanism in preventing me from taking on more personal projects that I really don’t have time for; my work next action list has remained pleasantly manageable. In fact, while I plan to continue tweaking the system indefinitely, I’ve declared the “adopt GTD” project at work a success, and I only have a couple of action items left on the home version of that project.

In a bit of a shocker, I not only just put up pictures from 2007, I even got around to putting up the pictures we have so far from 2008. No, I don’t like zoos as much as you might think from these pictures, I just found more stuff that I wanted to take pictures of in zoos than elsewhere.

Resizing that many pictures at once makes me understand why people like batch image-processing software; at least I’ve noted down the keystrokes to do it in GIMP, so that I won’t have to spend a few minutes figuring that out next time.

(Mostly an e-mail to the leandevelopment group, but I figured I might as well stick it here, too.)

I just finished reading The Toyota Way, by Jeffrey Liker. Which I highly recommend: it may actually now be my favorite (non-software-specific) lean book. A clear presentation of a good set of principles; I saw a lot that was new to me, still more that would have been new to me half a year ago (or a year ago or two years ago), I’m sure that I’ll get a lot out of it the next time I read it.

One thing that struck me in the software development context is its principle 13: “Make Decisions Slowly by Consensus, Thoroughly Considering All Options; Implement Rapidly”. It seems to me that there’s a pretty big tension between a naive application of that rule and agile: it sounds to me a lot more like BDUF than traditional agile.

Now, I don’t really believe that that’s true, partly for ideological reasons and partly because I’m sure that most people doing BDUF would do it in a way that is far away from the spirit of that principle. But maybe there’s something to be learned (in both directions?) from Toyota’s slowly building a consensus before deciding as compared to Agile’s quick iterations on development?

Part of the bridge seems to be set-based development. (Which is one concept in the Poppendiecks’ books that I haven’t seen in many (any?) other agile books.) Are there other Toyota techniques in this area that we should take to heart? The chapter talks about A3 reports; I’d been thinking that they might be a good fit to some gaps at work; does anybody have experience using them in software development? (Hmm, the Poppendiecks talk about those, too, don’t they? My copies of their books are at work, so I can’t check.)

One thing about agile that I don’t want to give up is that we’ve got some good techniques for evolving well-designed software. (E.g. Kent Beck’s four rules. Which I wish I could find a good URL for; this is the best I’ve come up with.) Are they in tension with the Toyota principle? Or are they each applicable in different domains?

How do I tell on a software project when we should be spending more time thinking before making a decision and when we should be getting our hands dirty and checking in production code? (With, of course, the expectation that the code will change as our understanding and the requirements change.)

Here’s the book’s description of the principle (emphasis in the original):

The Principle: Thorough Consideration in Decision Making

Many employees outside Japan who have joined Toyota after working for another company have had to face the challenge of learning the Toyota approach to problem solving and decision making. Because Toyota’s process of consensus decision making deviates so dramatically from the way most other firms operate, it is a major reeducation process. New employees wonder how an efficient company like Toyota can use such a detailed, slow, cumbersome, and time-consuming decision-making process. But all the people I have met who have worked for or with Toyota for a few years are believers in the process and have been greatly enriched by it—even in their personal lives.

For Toyota, how you arrive at the decision is just as important as the quality of the decision. Taking the time and effort to do it right is mandatory. In fact, management will forgive a decision that does not work out as expected, if the process used was the right one. A decision that by chance works out well, but was based on a shortcut process, is more likely to lead to a reprimand from the boss. As Warren explained in this chapter’s opening quote, Toyota’s secret to smooth and often flawless implementation of new initiatives is careful, upfront planning. Underlying the entire process of planning, problem solving, and decision making is careful attention to every detail. This behavior is associated with many of the best Japanese firms and Toyota is a master at it. No stone is left unturned. In fact, every stone is inspected under a microscope.

…

Thorough consideration in decision making includes five major elements:

• Finding out what is really going on, including genchi gembutsu.
• Understanding underlying causes that explain surface appearances—asking “Why?” five times.
• Broadly considering alternative solutions and developing a detailed rationale for the preferred solution.
• Building consensus within the team, including Toyota employees and outside partners.
• Using very efficient communication vehicles to do one through four, preferably one side of one sheet of paper.

(Liker, The Toyota Way, pp. 238–9)

As I have, perhaps, alluded to previously, we spent the second half of April in Paris. Notes:

• It’s the most wonderful place in the world, but I’m actually not feeling particularly compelled to visit it again any time soon. Some of this has to do with the fact that I’ve been there eight times; some of this has to do with the fact that I rather enjoyed spending the week between Christmas and New Year’s at home, and am not sure how much I want to do any vacationing for the sake of vacationing. Of course, this is all subject to change at any time, and Liesl and Miranda may have different opinions.
• We’ve had bad hotel luck in the past; based on recommendations from comments on this blog post, we decided to try renting an apartment this time. We went with absoluliving; not as cheap as a cheap hotel, but for the same price as a decent hotel, we could get two bedrooms and a living room, with a clothes washer, a stove (not that we used it), a fridge. Or at least we thought that’s what we were getting; the day before we were supposed to leave, they e-mailed us to tell us, with no explanation whatsoever, that they were changing apartments on us; we ended up in a one-bedroom apartment, which they had the gall to call an upgrade because it was in a trendier neighborhood. To be fair, the apartment wasn’t a complete unknown, since we’d marked it as acceptable from the list of apartments they’d initially proposed to us, but I still didn’t appreciate the bait-and-switch, or whatever it was, at all. (Also, to be fair, I’m happy enough with the area we ended up in, and will consider staying near République in the future, but I didn’t like being in the middle of a very long block on a side street.) The other problem with the apartment was that one window kept squeaking open and closed all night when it got really windy; I’m not really mad at them about this, because I’m not sure how they would have discovered it by inspection, but it does point out a problem with an apartment agency that you don’t have with a hotel, namely that you can’t just complain about a maintenance problem and have them move you, because they might, say, be closed on the weekend. (Fortunately, it happened on a Thursday, and they managed to get somebody in on Friday who eventually stopped the squeaking by duct-taping it shut.) Anyways, one separate bedroom (Miranda was in a sofabed in the living room) is vastly better than everybody sharing a bedroom, so the general idea was a good one.
• Poor Liesl was sick some of the time; fortunately, it wasn’t nearly as bad as when we were in Amsterdam, but she stayed in the apartment for three (two?) of the days because of that. Partly because of that, we didn’t go to as many restaurants as we might, but we still got some good food out of the trip (including one from a restaurant that apparently changed hands about a week after our last trip and was completely, surprisingly different this time); visiting salons de thé in the afternoon may have been my favorite part of the trip. (The pizza at decent Italian restaurants in Paris is quite nice, too.)
• Why had I never heard of Lovis Corinth before? My first reaction is that I’d rather look at his art than, say, that of Van Gogh or Gaugin or Seurat. Looking at labels suggested that part of the reason is that his art is scattered around museums in Germany instead of clustered in museums in Paris; glad I’m aware of him now.
• The baboons at the zoo in the Bois de Vincennes are a hoot.
• Having internet access in your apartment is a good thing. And no, this is not a sign that I need to relax and tear myself away from the internet: this is a sign that I don’t feel compelled to spend every vacationing hour traipsing from site to site and can, instead, spend time in my hotel just enjoying myself without feeling guilty that I should be doing more on vacation.
• Having a washing machine in your apartment is also a good thing. And points out another benefit to the internet: if your washing machine is refusing to wash and just blinking when you hit a number, you can google the model name and get a manual. (Answer: you accidentally hit the child lock button; hold it down for four seconds to unlock, and what you thought was the off button is actually the start button.)
• Miranda’s favorite museum turned out to be the sewer museum.
• Sacré Coeur is distinctive to look at from a distance but boring on the outside. Not so Notre Dame: there’s something to be said for thousands of people working for hundreds of years to produce something glorious.
• I really am not impressed by the current Orangina ad campaign: large-breasted zebras just don’t do it for me. Sex, fine; animals, fine; combining the two, ick.
• We forgot to buy a power converter; fortunately, the basement of BHV had them for sale. (They had one that went both directions, 110-to-220 and 220-110.)
• Traveling with several puzzle books from Nikoli was an excellent idea: not only are the puzzles top-notch, but the narrower-than-US form factor meant that I could slip one into my jeans pocket, which is very useful when walking through museums where I’ve had to check my backpack, finding myself a room or two ahead of Liesl and Miranda because we go through them at a different pace, and needing to amuse myself. I’m getting a bit burned out on Nurikabe (though I still think they’re an excellent puzzle variant), and Number Link isn’t my fave (once the puzzles get out of the easy range, I have a hard time proving my solution is unique, which frustrates me), but I’m still a big fan of Masyu and Slitherlink. I’ll have to try some of their other puzzle types.
• I really can dial down the number of books that I take on a trip these days: I have enough other entertainments that I don’t need to carry nearly as many to avoid running out of them. (And there are always bookstores if I guess wrong.)
• Heavy curtains are great for the first night or two after getting off the plane, but in retrospect I should have stopped closing them completely after that: I never really got my clock adjusted to Paris time. The flip side of which was that lying awake at night gave me lots of practice in going over my Joyo kanji…