Electioneering

In a moment of zest, I took a few minutes aside to write my local legislators about an issue which concerns me, which is our voting method. Few people are aware of the effects that our voting method have on politics, or even that there are alternatives. But there's a growing grass-roots movement of people who recognize the benefits of better voting systems, such as Instant Runoff Voting and Condorcet Voting Methods (such as the Schulze Method). Why should you care about the voting method? Well, one of the many good reasons I didn't discuss in my letter is that our voting method makes us stuck with choices we don't like, and it picks a winner who is often not the best candidate in the eyes of the electorate. For example, look at the federal landscape today. Not one branch of government has an approval rating above 30%. Wouldn't it be nice if we could have only the good Democrats and only the good Republicans, or how about someone in the middle? But you can't do that, you're stuck with just 2 choices, and there's a reason. At the core of it, is the Spoiler effect. This is what comes into play when a third candidate 'spoils' the election toward the least-preferred candidate, as Nader and Perot in these past few elections. Basically, a rising star builds up their momentum up until the moment when they split the vote enough to spoil the election, and at that moment, their very constituency turns against them. I witnessed this first-hand in Austin, where the liberals vilified and actively opposed Nader's efforts in 2004, even though they agreed with him, because they believed he had spoiled the election to Bush the Younger. This whole process is known as Duverger's Law, and this is the reason people speak of our system as a "two party system." This is, as they say, a bug, not a feature, that is, it's a flaw in our system, not something we've taken on by choice. Another way of looking at this is through the academics' eyes, who call this the voting criterion of Clone Independence. Basically, 'clone independence' is the question of what happens if you taking an existing race, clone one of the candidates, and carry on the race with the clone included. Different systems react differently. In our system, plurality voting, the clones together are less likely to win than the original on their own. For example, 2 qualified liberals or 2 qualified conservative are actually less likely to win than a single qualified liberal or conservative. In others, they may be more likely to win. The proper answer though, is that they should collectively have the same chance of winning as the original did on their own, and their are several systems like that. Including both Instant Runoff Voting, and my personal favorite, the Schulze Method, for which I prefer the name 'Full-Runoff voting.' In any case, for those of you frustrated with what's going on, I recommend you pick a subject which has local significance, because your voice is 100x louder when you speak to your local legislators, who have far fewer constituents. Go to your legislators, show your interest, and speak to them on the specifics which actually affect their constituents, which they recognize could affect their chances of re-election. As a politician once said, whether they agree with you or not, "when I feel the heat, I see the light."
Dear [Mr./Mrs. Legislator], I hope you'll consider supporting Instant Runoff Voting, aka Ranked Choice voting, ala [HB 2202/ SB 6000], which I'll refer to as IRV. If you're unfamiliar with IRV, it's a form of voting which allows the voter to rank each of the candidates according to their preference. At the time of tabulating the votes, if no candidate has a majority of first-choice votes, the candidate with the fewest first-choice votes is eliminated, and their votes are re-alloted to the second-choice candidates of those voters. Candidates are successively eliminated until one of the remaining candidates has a majority of votes. It may not be obvious from my telling, but IRV presents the opportunity to solve several of our problems in Washington at once. First of all it removes the need to limit choice through the restrictions of the pick-a-party primary. This is a problem which has been generating frustration on the local level across Washington, as evidenced by Pierce County's adoption of IRV to solve just this problem. Second, it ensures that all our elected officials must win the support of at least 50% + 1 of the electorate in order to be elected. Not the out-right support mind you, but enough to put them out ahead of their other major opponents. In many local races this makes a significant difference, for example at the Port of Seattle Commissioner election just a few days ago, Place 2 was won with just 33% of the vote! Only a third of voters supported that candidate (Gael Tarleton) and yet she won. Likewise, Redmond's mayor was elected with 39% of the vote, and had strong opponents with 36% and 24% of the vote. It's very possible that more of the electorate actually preferred the candidate who received 36%, but were unable to have there preference heard, because of our limited voting system. The principles of representative democracy suggest we can do a better job of forming a consensus for who to choose as representatives, and IRV can help us do that. I've spoken with a number of people about this, and just about everyone I've spoken to thinks its a great idea once they know about it. It's encouraging that Pierce county has voted to adopt this method, and it shows that there is a grass-roots movement growing up around the issue. I hope you'll be there to work with that movement. I'm looking forward to working with you on this issue, and I'm happy to answer any questions you might have. Regards, Ben Woosley P.S. Another alternative to IRV, rather than eliminating the least popular candidate each round, uses the voters' ballots to run a "virtual" runoff between each and every pair of candidates, simultaneously. The candidate who beats each of the other candidates in this "virtual" runoff is the winner. In the rare case there is not a single candidate who wins all run-offs, IRV-style elimination rounds are used. This is known as Condorcet's voting method, and is technically better than IRV. Both are much better than our current system.

Consistent Inconsistencies

I'm faced with an interesting decision for my last semester of college. I'm required to do a senior design project, which might seem like an excellent chance to do whatever I want, but unfortunately the UT assumes ownership of any IP developed through the project. This means I can't or rather, won't, use any of my pet projects. As it would happen, I'm left with two very different options. The first is to take on a very bold, challenging project with a good friend of mine. The subject has just recently emerged into the main-stream and promises to be very important for at least the next five years. It's enticing, but possibly would be too much to handle well, in addition to my own projects, work and classwork. So I'd have to drop something else to accomodate it... The second option is to work with my current employer, SigmaTel, on a project which is useful and will be interesting in the sense that it's my code that I "own" that I've written and designed from scratch. The problem is interesting but lacks the gee-whiz factor of the former project. Of course there's a big bonus in the fact that I'd be getting paid to do it for SigmaTel. And, in the end, combining work and my Senior Design project will make for a much more livable semester, and may even give me more time for my other exploits. So, in review, I'm selecting a semi-mundane, paid-for project over a bold, daring (but possibly over-reaching), unpaid project with a hot new technology. So am I selling out? Should someone with bold dreams throw caution to the wind and take on the big problems, no matter what?

My (possible) future as viewed through other peoples' lives

One cool aspect of the public nature of the web, is that you can watch some of the most effective people up close. For an aspiring hacker, this leads naturally to measuring oneself against their accomplishments, or to be more exact, comparing what you've done to what they'd done at your age, or vice versa. I've done this, with some mixed results. For example. Aaron Swartz is a number of years younger than I, and he has, among other things, just released his first web framework. On the other hand, I've five years left before I have to achieve the like of Ruby on Rails creator David Heinemeier Hansson. Now one could ask whether I actually expect to do so. I honestly don't know what I'll do these next few years, but I do know I won't do much if I don't aim to do much. That said, there's a refreshing familiarity to the thoughts I read in Hansson's "Loud Thinking," particularly the early years. What more indication do you need? ;-)

I U+2764 Unicode

As always, I've been working on a random side-project, and lately, I've been learning to appreciate Unicode. Specifically, the rude awakening of having to deal with various character encodings rather than plain ASCII text. Of course, now I can say something silly like Oh '0x92', this must be good ol' 1252. But having to carry this sort of arbitrary knowledge around is a bit silly now, and will be all the more silly as people interact more across languages and cultures.

For now, it's a fact of life, and I know we can all learn to deal with it. But I'll be working toward the day when, we'[ll] take Unicode for granted and cheerfully accept things like perl variables called $¶, the URI http://alþing.is/þjóð/, and people named Zoë.

Until then, you can wear shirts like this one. Now, I'd like to point out here that the so-called Mac version is more correct. The diamond with inset question mark is actually a unicode character for "replacement character" (U+FFFD). Both Windows and (Gnome) Linux get this wrong (for now).

It's off to California for me!

I'm not big on introductions, so I won't bother saying anything about myself. Best to watch and learn anyway, I would think. In that spirit, a bit about what I'll be up to for the next week.

I'm leaving tomorrow for San Francisco, California, where I'll be attending Apple's Worldwide Developer Conference 2005. For six of seven days there, I'll be coding, learning and meeting new engineers, not just any engineers, mind you, but the kind who understand and appreciate the beauty that is Apple. While there, I'll be staying with a good friend of mine, Robert, who happens to be interning for Apple this summer. A job I would have liked to have myself mind you, but I do well enough anyway. There's time for that story later.

I rarely ever do anything big like this with fewer than three reasons for actually doing it, and I can count about five as of now, there's 2 listed above, another is that I've recieved a student scholarship to the conference so that it will be free, another is that I will be able to borrow Robert's PowerBook while there (the very machine which got me interested in the company). I also have heard plenty of great things about San Francisco, which, as far as I know, is Austin (TX), and then some. That is saying plenty. Oh but there's more. With the big Apple conferences such as this one, there is usually a keynote speech delivered by none other than Mr. Steve Jobs himself. At these things, there are wonderful new things showed off and new products released. The iPod itself was released at one of these things, years ago, not to mention the music store. This will be my first opportunity, ever to witness one of these events live and in person. This comes after years of following these event live via internet, and once via live satellite feed on the U.T. campus.

But wait, there's still more. In San Francisco, there happens to be a place called the "Exploratorium," which I've been advised to visit. I was told to do so by a U.T. professor, Dr. John Pearce, who works in medical instrumentation I understand. I was speaking with him about an idea I had, a project I continue to work on, hoping to gets some input, what ever suggestions might come my way. One of his was to visit this place, as he says there's an excellent explanation of the function of the human vocal folds and all of that stuff, which, you'll learn, is important to my project. He even told me to track down an old issue of "Nova" on the Exploratorium, if I could. Well, now I don't need to.

So there you go, but aside from all that, of course, I expect to have a good time, so I'll be hitting up whatever bars and clubs I find that suit me.

All in one week! How am I ever going to sleep? Well that's another story...