I’ve been trying out OKCupid recently, and while entire essays, if not books, could be written about the experience, the questions it asks, and the way it asks them, is an issue for me. It’s not that the questions are weird or repetitive, or seem bizarrely unlikely to result in reliable rankings, all of which is true, but that the manner in which the questions is phrased is technically poor.

First thing to review is how OKCupid asks questions. There’s a bunch of questions, you pick one answer for you, then pick as many answers as you like that are acceptable for a potential match to give. My first issue is simply with the phrasing. Many questions ask if I would “consider” doing something. There seems to be a wide range of interpretations of what consider means.

The next issue is that many questions are too indirect, like “Would you date a smoker?” I don’t smoke, but I may say yes. But another non-smoker may only put no as the acceptable answer, rejecting me even though I don’t smoke. The direct version, “Do you smoke?”, seems like a major improvement. Lots of questions are like this. They seem designed to determine not just how intolerant I am, but how intolerant my match must be. The fact that people who are 100% compatible but differ only in their tolerance for incompatibilities could be rejected seems like a flaw to me, but maybe that’s the magic to a good matching algorithm.

Another drawback of some questions is the frequent necessity to invert the question when picking acceptable answers. A question about height that can be answered “I like to be taller” or “I like to be shorter” is a good example. The acceptable answer should be the opposite of the picked answer. In fact, there shouldn’t be a need to identify acceptable answers for such questions. People don’t seem to do a good job with the logic here. Arguably, I shouldn’t be concerned because I’m not much interested in people who fail at logic, but it clearly reduces the efficiency of the matching system as a whole.

I notice that the latest round of Windows Updates includes a Thinkpad Display 1400x1050 update. And there’s a link for details. But following the link tells me that Winqual has moved! Follow the new link and I’m redirected to a sign in form for the Windows Developer Center Dashboard. Seriously? I have to sign up as a developer to find out what a recently installed driver update does? That sounds like something an open source operating system would make me do!

Have I mentioned I hate how Google Accounts work? Today I noticed I was still logged in while looking at some movie showtimes. Clicked logout. The page goes blank, the browser follows a couple redirects, and I wind up back at the same page... Still logged in! Other people complain they’ve been locked out of their Google accounts, I’m locked in.

A critical feature for me was offline access. Not “I hope my IMAP client cached that email” offline access, but real “I can read any email, ever” offline access. The problem is that every client I’m familiar with that could do that basically worked locally. The price paid for offline access was single computer access. In theory, multiple desktops could fetch mail and process it, but the tags and filters would get out of sync. I don’t know anyone who has pulled this off. I needed to build a system where despite running independent clients against independent mail stores, the state of the universe would be kept roughly in sync.

more...

Sinatra (the ruby web app framework) has a handy method to indicate that the response is an attachment and should be saved: attachment filename. It even sets the content type correctly. Unless it can’t guess from the filename. Then it throws an unrecoverable error.

Discovered this little fact trying to download a .tgz file. The documentation says if I find a mime type Sinatra doesn’t understand, I’m supposed to run mime_type :tgz, 'application/octet-stream'. OK, great. So where’s the list of already known types? Never mind that, I’m really supposed to make up a list of every mime type I might want to download at some point and register them all up front? Insanity. In theory, I think rack is supposed to already be using a default of application/octet-stream, but it appears I’m just unlucky.

Following up on the previous post about software reliability, let’s consider the concept of utility functions. There’s a few definitions for utility function, but I’ll say it’s something along the lines of a function that maps the raw measure of something to its value to the user. A common example given for money is the natural log function, which explains why a dollar to a millionaire is worth less than a dollar to a poor person, even though the raw measure ($1) remains the same: log(11) - log(10) > log(1e6 + 1) - log(1e6). Law of diminishing returns.

more...

OpenBSD 5.1 preorders are now up on the site. And minix 3.2 was also released recently. Here are some reflections on why microkernels don’t matter. I’m not saying microkernels are worse, or slow, or anything like that; they just aren’t that much better. There’s a somewhat long two part argument coming up. One part is that microkernel reliability is overstated, the second part is that the value of reliability is itself overrated.

more...

This post is rather delayed, since I quit using gmail almost a year ago, and the decision was made more than a year ago, but since I’m hopefully going to start writing about my post gmail adventures, I’ll start at the beginning.

Gmail was, for a time, pretty awesome. It was certainly an upgrade from pine in many respects. The ability to open attachments without bizarre scp contortions was a plus. I don’t really need to recount the virtues of gmail, but I was impressed with it for quite some time. First (and only, really) web app to replace a desktop app for me. But Eden was not to last.

Over time, I had a growing spam problem. No matter how many Chinese emails I flagged as spam over the course of five years, gmail was convinced that this was the day I woke up knowing Mandarin. Also, based on observed behavior, gmail whitelisted all emails with the word “lottery” in the subject. This was kind of a slow burn pain.

Also, the filtering options were kind of limited. Basically, too many annoying mailing list people and not enough tools to deal with them. I could block senders, one by one, somewhat tediously, but no good way to kill a thread. This was kind of a spiky pain, really bad some days, less intense other days.

Finally, there were some service disruptions or shortages or whatnot. Every time I clicked an email and did not get to see the email just stoked the fire a little more.

Things hit the bottom after I had already made the decision to quit. When it was just personal email in gmail, I was limping along, but once we started using gmail for work and I had to start using two browsers to keep things straight, the pot really boiled over. See also my other post on that.

In the end, I decided the only solution was to write my own mail client, because there are not enough of them. As far as I was concerned, gmail was the best available, and it’s just not that good. My replacement, since named mailtanium, was built to be fast and flexible. I’ll introduce it in another post.

I didn’t know about the Shakespeare play before learning of the movie, but it sounded interesting. It’s a modern adaptation, updating the setting to the present day. Such adaptions may not please everyone, but it works. Really well, in fact.

Prescient is the wrong word, but it’s the first impression I had watching Coriolanus campaign for consul. Timeless, maybe. The modern update helps drive this home; a period setting would have allowed the viewer to dismiss the story as not here, not now. His campaign goes about as well as I imagine my presidential campaign would go. I don’t know if the timing of the movie to coincide with the primary campaigns is deliberate, but it’s apt.

My first kindle fire, back in November, lived for about two hours. Then I updated it to software version 6.1 and it was forever after frozen at the startup logo screen. Amazon kindly sent me a second fire that survived the update, which I had been using more or less happily for the past month. More happily because I can view pretty pictures and movies with it, less happily because the interface was super slow and unresponsive. About a million reviewers have said much the same.

Today, that second kindle fire apparently tried to update itself to version 6.2. Tried and failed, or as some people like to say, tried and died. Same symptoms as the first go round, frozen at the startup logo. Supposedly, this was the update that fixed the UI response issues, but I’ll never know. This time it’s going back for a return, no replacement. Maybe I’ll try again in a year, but if I need to get a new device every time there’s a software update I’ll pass.