Saturday, September 18, 2010

New city, new bike

A few facts. In May, I moved to Seattle. Since May, I have used my bicycle twice. As of this fall, I will be using a bike pretty much every day. Read on for an explanation regarding the last two facts.

Why didn't I ever use my bike during the sunny season in Seattle? Well, I had to commute to Microsoft from Capitol Hill. This is a very inconvenient task regardless of the weather for a number of reasons. There is no direct cycling-only option to get from the north half of Seattle to the SR-520 corridor. The options were as follows:
  1. Bike to the Montlake Flyer Stop, a final eastbound west-side stop for congested bus routes such as the ST 545. From there, ride the bus across the bridge, disembark at the first stop and ride to Microsoft for 20 minutes along the SR-520 corridor multiuse trail. This is a huge pain because you must wait for an empty bike rack on a bus, which could take half an hour or more after 8am.
  2. Bike all the way up the Burke-Gilman trail and then on roads through Kirkland to Redmond. This adds at least 45 minutes to the commute.
  3. Bike south to I-90 and use the bike lane attached to the interstate. This is the nicest way to cross the lake, but it is quite out of the way unless you live in or south of Central District. You also have to deal with the Bellevue's traffic and its general abundance of jerks with cars while going north to Redmond. This detour adds a minimum of 30 minutes to the commute each way.
All of these were way too much hassle for myself, especially considering my tendency to keep long hours at my internship. As I've been too tired/busy to go out on long rides on the weekend, the racing bike has sat on the porch most of the summer. My daily commute was a 20-45 minute one-way exercise in sitting my rear on a nominally soft Sound Transit coach seat.

Now that the internship is done, I feel at liberty to realistically consider commuting by bike to UW* every day, including rainy and dreary days. The main considerations are the different weather conditions (rain, mist, fog, slog, and Seattle's other precipitation variants), a significant hill climb when going back home, and suitability for commuting.

The aforementioned "racing bike" is a Felt Racing 2008 Z80 (sized 54cm, a tad too big for me). I inherited it from Steph ever since she started her romance with her fixed-gear bike. Since it is explicitly a "racing" bike, it does not have clearance for tires much larger than 700x24, and fitting a rack is out of the question. The frame geometry is a bit compact, which isn't great for touring or commuting. It does well on hills with three chainrings (50/39/30) and a Shimano 9-speed cassette (12-25T), but the Shimano Tiagra STI shifters are really not my style. The derailleurs/cogs frequently get confused for no apparent reason, and perform very poorly with chain tension (say, going uphill and gearing down is somewhat risky).

On advice from several other bikers, I started my search for a commuter bike with the Surly Cross Check. It's a steel-frame bike designed for maximum flexibility, and commonly employed as a commuter, cyclocross, touring, and "whatever" bike. I was initially skeptical that it would be much different from the Felt bike, but good geometry and steel can make a world of difference.

Over the past two weeks, I tested a 50cm Cross Check (at REI Seattle), a 52cm Surly Long Haul Trucker, 50cm Aurora, and finally, a 52cm Cross Check. I'm planning to go back and buy it on Monday from Counterbalance U Village, and then take it to FreeRange Cycles in Fremont for some adjustments. The most important adjustment will be the addition of a 3rd chainring. This will enable me to get up hills.. something that is not really possible with the 2 chainrings (36, 48) x 9 (12-25) that come standard on a built up Cross Check.

The next part in getting commute ready will be to shell out for fenders, a rack, and panniers. I'm not completely settled on the brand of panniers that I want, but at the least they have to be waterproof and able to fit a 15" macbook pro inside a case :) I will update with pictures once the goods are purchased come Monday.

Tuesday, June 8, 2010

PLDI 2010: Day 0 and 1

As I write this, I'm at the Fairmont Royal York hotel in downtown Toronto, the location of the PLDI 2010 conference. Our paper from Purdue ("An analysis of the dynamic behavior of JavaScript programs") was the first paper of the opening session of the conference. Though I am not a presenter this year, I felt that it was important to come to this conference for networking and to see what's going on elsewhere.

So far, Toronto has been good. I found some very cheap lodging at the University of Toronto. Apparently they operate their dorms as short or long-term hostels during the summer, and I was able to stay at $37 CAD a night. Compared to the conference hotel (a 4 star hotel), it's a great steal and has allowed me to rationalize the exorbitant price of dining in Toronto. Transit in Toronto is much more institutionalized than in Seattle, so the subways are often packed in the morning and streetcars go between the most important subway stations and offer free transfers to the subway. Though I have gotten lost a few times in the subway, it is much more convenient than being lost on a bus system or on foot.

I arrived here on Sunday via a non-stop Air Canada flight from Seattle. Transport from the Toronto Pearson airport is a simple connector bus and 15 subway stops, for a grand total of $3 CAD. The price of food has a great deal to do with its proximity to 4-star hotels; A half-dozen blocks from the conference hotel, I was able to get decent coffee for $1.50. Within the hotel, coffee is over $3 and a simple Heineken at the hotel bar will run you a sweet $8 CAD.

Downtown Toronto also has a sprawling network of underground shopping plazas and walkways. According to the marketing copy, it is the largest underground network in the world. Personally the city seems like Montreal, but much more British than French (opposite of Montreal). Montreal also has a substantial covered/underground tunnel system, but I never used the subway there. The French influence in Montreal is almost like the Chinese and Vietnamese influence present outside of the downtown core of Toronto. On Sunday I walked through Chinatown, and it is at least 30 blocks in size. It makes the International District in Seattle seem quaint and cozy by comparison.

Later I'll write about the actual research presentation program. Now, I will be off to lunch.

Tuesday, April 27, 2010

Covered bicycle parking at Purdue University's West Lafayette campus

Purdue has very little biking culture. Thus, the poor state of affairs when it comes to bike lanes and bike racks is not surprising. Bike lanes deserve their own post entirely, because there are so many ways that they could be improved.

It seems that the vast, vast majority of bikes on campus were bought during freshman year by mommy and daddy at WalMart, and have never been serviced since. Rusted-out bikes are common, and the relevant groundskeeping/police people only remove abandoned bikes twice per year (at the end of Autumn and Spring semesters). Also, there does not seem to be any coherent approach to bike racks: some are long racks, some are upside-down U's cemented into the ground, and there are a few truly eccentric bike racks in the older parts of campus.

By far the biggest gripe that I had was the lack of covered bike parking, especially outside of residence halls. For those poor souls in Owen, Tarkington, and other dorms without elevators, it is not even possible to bring your bike into your tiny room. Even in halls with elevators, there is no place to securely store your bike besides your room. Without covered parking, bikes both cheap and expensive will quickly deteriorate and become unusable without a new chain and other parts. Since replacing such parts on a Walmart bike is not usually possible, these bikes are abandoned, taking valuable space in heavily used locations (like dining courts, lecture halls, and dorms).

In my four years at Purdue, I have only come to discover a few places where one can reliably park their bike at a bike rack with shelter from the elements. If anyone knows of more, please let me know and I'll add it to this list. I do not spend much time in dorm-land or Engineering parts of campus, so it is likely that I have forgotten a few places.

  1. Beneath the elevated building spanning Wetherill and Brown. There are at least four bike racks, but they can be crowded at times. Similar to the Math building breezeway, rain/snow can fairly easily blow through and still get bikes wet.
  2. In the Hawkins Hall underground parking ramp. Just to the right upon going down the entrance, there are two bike racks that are a decent distance away from the outside of the garage. This place seems popular with old commuters (saw lots of bikes with 2+ panniers).
  3. There is some marginal covered parking for bikes in front of Krannert. There is an overhang about 8-10 feet up in the air and some load-bearing pillars. Amongst this are some bike racks. A bike parked there would probably get wet with much wind, though. Another minus is it's proximity to the campus bars; left for too many nights, it would be a likely victim of drunken destruction.
It would be an easy fix to add more covered parking near campus: simply remove a few parking spaces in each of the parking garages, and add modern bike racks. While this would remove about a thousand dollars a year in A parking revenue, I'm sure that the cost of removing and disposing of hundreds of bike frames and kicked-in wheels. Simple awnings are inexpensive, and can be used at several existing large bike rack areas without making the landscape substantially uglier. I'd much rather see awnings than rusted, abandoned bikes.

Wednesday, April 21, 2010

Slowly improving my ergonomic-ness

One of my coworkers in the lab recently decided to start back up on his piano-playing. Naturally, I was jealous (why did I never learn to play piano?). However, within a week he came into the lab bearing wrist braces and a grimace. Between learning Chopin and coding for 8+ hours a day on a 13" MacBook, all of the finger work finally did him in. He was unable to bend his wrists at all while wearing the braces, so he had to buy an ergonomic keyboard that doesn't require bending of the wrists.

I have always been slightly curious about exotic keyboard layouts and ergonomic ways of working, starting with my learning of Dvorak layout last year and continuing when I saw several people at UW with fancy Kinesis keyboards. Since that visit I have been debating whether or not I need to worry about ergonomics, and if I do, what to do to alleviate this worrying.

For starters, I have tried various different ways of using my MacBook. Despite being the midsize model (15"), it is very hard on your wrists to use the cramped keyboard for extended periods of time. This is compounded by the abundance of chairs and tables on Purdue's campus that make good posture difficult or impossible. The first experiment was to try sitting up straight. This only is comfortable in a small number of chairs on campus, so my tried an entirely different approach to typing posture: standing up while typing. This is also hard on campus because most tables are quite short. This has only worked at home, where my dinner table is designed for high chairs.

The next step, one which I am currently in, is experimenting with keyboard and monitor height. My other main gripe about laptops (besides cramped keyboards) is that they force you to look downwards at the screen. This makes it very difficult to maintain a good posture while typing, since your neck is bent forward and head downward. My first attempt at fixing this is to buy a somewhat cheap ergonomic keyboard (the bog-standard, entry-level Microsoft ergo keyboard). With this, I can adjust the height of they keyboard and the laptop screen independently. It will take me a few days to get used to using an external keyboard again, as I never use a mouse these days.

I'm wondering what the long-term, optimal configuration will be. This is important to consider before I spend a lot of money on other equipment, and before I start graduate school and set up my student office. Does the split keyboard/screen necessitate having a desktop for long-term work and a laptop for short-term work? Is it worth it to have ergonomic setups at both work and home? It's fully possible to drive two external monitors with my MacBook Pro's video card, but all of the setup and takedown is a barrier to starting work easily. At the same time, I don't know if i'll be able to get a nice monitor and a decent Mac Pro or iMac in the graduate student offices.

I suppose time will tell. In the meantime, i'm going to continue improving my standing-while-typing posture, and hope that someday down the road I will not have to deal with the occupational hazards of hacker/programmer (as my poor coworker must deal with now).

Thursday, April 15, 2010

A new way to handle email

For the past four years, every day has brought a stream of emails to my inbox. Some days, this stream resembles a trickle (such as on break, or on the weekend). On the weekdays, it often approximates a torrent. My strategies for diverting and handling this torrent of obligations, requests, and information has changed every so often. My goals in these incremental changes of process are to 1) minimize the time needed to find past emails 2) minimize the mental overhead of keeping track of the status of emails, and 3) minimize the time needed to maintain the system to make 1) and 2) possible.

In the past, I had a low volume of email to deal with, so I had a boring method of handling email: upon new mail arriving, I either replied to it or left it alone. After a few days or weeks, I would get tired of scrolling through my inbox. Some of the emails could be easily deleted or archived in a folder, but there were always some emails that were not yet "done". Perhaps they merited a long and thoughtful response that was yet short and ill-conceived; perhaps they gave details of an upcoming event. The easiest thing to do was to use the inbox as a holding pen until these messages became 'resolved'. This strategy worked well until senior year, when I became wrapped up into so many different events, ideas, and mailing lists that my inbox would still be at 30 messages full after being "cleaned".

I've decided to use this new approach, called the Trusted Trio.

Basically, you segment your email into three categories which explicitly model the lifecycle of an email. I'll call these categories "TODO", "In Progress", and "Archive". The first category is for emails that can't be responded to in a minute or two and need more time to be dealt with. This includes emails requiring long responses, some (external of the mailbox) action, or otherwise require me to do something.

The second category, In Progress, contains messages that require a later follow-up, pertain to a future event, or are no longer TODO but not quite dead yet. If you were to have an exchange with someone to set up a lunch, and were awaiting a reply of their preferred times, the entire thread would go into "In Progress".

The final category is for emails that are done, dead, or most likely no longer alive. Depending on the email client, you can organize this however you like: with a tagging-based email client (i.e. GMail), adding subject tags is a sufficient amount of organization. I use and MobileMe right now, so I use folders based on what part of my life the email pertains to. The current subfolders include Research, Personal, Shopping, Class.

My main problem with this new approach is that it gets messy with several different email accounts. Right now I have a half-dozen emails and many more redirection addresses (such as,, and so on). It is difficult for me to funnel all of these into a single IMAP email account, especially when i'm not in front of my laptop. Hopefully when I start at UW, most of my emails will slowly come by just one or two accounts.

Tuesday, April 13, 2010

Concert Review: Miguel Zenón's Esta Plena

NOTE: this review was written as part of MUS 378 Jazz History, taught by Don Seybold.

Miguel Zenón’s Esta Plena. To me, it sounds like the name of a Spanish ballet. I have listened to music from Cuba, Mexico, South America, but plena is none of these: it is the traditional music of Puerto Rico. Still, knowing just this did not meaningfully inform my expectations of the concert. I discerned it was something unfamiliar and different, on account of the unusual number of young people packed into the ground floor of Loeb Playhouse. My seat was towards the rear, and behind me were perhaps a half-dozen young Puerto Ricans. To my left and right were more college students. There was a buzz in the air. It induced students to text and tweet at a furious pace, which added yet more energy and tension with every character pecked.

After the obligatory Todd Wetzel introduction, the band quickly deployed to their instruments and began playing without hesitation or introduction. Hans Glawischnig, the bass player, set up a boisterous Latin beat that enunciated the frenetic energy buzzing in the hall. The six seated behind me possessed the voices of a dozen, whooping, yelling, and otherwise emulating the soundtrack of a dance party in Spanish. As the theme of the first song was repeated, the younger subset of the audience met the beat with a steady clap. This was my favorite style played during the night: raucous, fast, and a distinctly “concert” sound (as opposed to upper-case Concert).

The concert’s theme was an exploration of plena – a music influenced by Spanish and African musical traditions. The main instigators of this sound were the three plenera (hand drums) of various sizes and their players: Héctor Matos (requinto, the smallest drum), Obanilú Allende (vocals and segundo, the middle drum), and Juan Gutiérrez (seguidor, the largest drum). The ensemble providing a jazz counterpoint to this trio consisted of Miguel Zenón (Alto Saxophone), Hans (bass), Luis Perdomo (piano), and Henry Cole (drums).

Merging plena and jazz is a nice idea in theory (on this basis Zenón was awarded Guggenheim and MacArthur grants), but it is a very ephemeral and fleeting moment in practice. On some of the numbers, the two styles were intermixed; others were more theme-oriented, with some themes played by the plenera and some by the piano or saxophone. The height of the concert was the long drum solo that traded attacks with the plenera, yet mostly sidestepped reusing tedious drum solo clichés. The main problem I sensed was that the drum rhythms are fixed and the folkloric quality of the music is much more structured than the floating-in-space harmonic aesthetic I often imagine while listening to modern jazz.

Regardless of the style, all performers were drenched in energy, whether improvising a solo or beating the living crap out of their hand drums in hard-to-imitate polyrhythms. Not since I saw Thom Yorke of Radiohead live have I seen a band’s frontman dance so wildly and without restraint while singing and playing. Miguel’s solos are plain as day to understand: just watch his body wobble about the stage, and match the motions and emotions to the movement in the music. The band’s energy was infectious, and throughout the concert it provoked yelling, clapping, and other concert-worthy (lowercase-c concert) forms of participation.

Unfortunately, only a small percentage of the audience was interested “experiencing” the groove, so most members just sat calmly (as if watching a YouTube video, or in a master’s clinic). Part of this is Purdue’s concert culture: when most of the concerts are sponsored by the local retirement home megacomplex, you shouldn’t expect many people to dance in the aisles. I would have much rather seen Zenón’s septet in a club with a dance floor, as plena music (and Latin-sounding beats in general) are undeniably designed to induce dancing.

To balance out the plena, several more typical jazz songs were also presented. The most pleasing segments of these were the improvisations of the piano and saxophone. None of these songs were terribly memorable for me, and I felt that they bored the P.R. audience as much as the plenera-wielding musicians who didn’t have a single note in some pieces. One exception was a ballad piece, which was quite haunting. It began with a simple riff by Hans on bass, and slowly added in complexity. With each new chorus, Miguel dug just a bit deeper into the theme, and by the climax was dancing passionately with his horn. It reminded me instantly of Bolero – but translated into the context of a jazz ballad. Rarely have I felt more compelled to stand up and clap after the final bars.

The concert was a blast. I’m looking forward to new works by Zenón, and am especially interested to see if he can further integrate plena tradition into the improvisations of jazz.

Monday, April 12, 2010

Quick tip: disabling iPhoto sync

I've always wondered why iPhoto always opens when I plug in my iPhone. It seems counterintuitive, considering Apple's obsession with minimizing options and optimizing for the common case. Chances are high that I don't want to import any photos from my phone when the battery is low, there are no new pictures, or it is way past my bedtime. If I wanted to import photos, I would open iPhoto myself! This has led to constant frustration and interruption of my flow.

It turns out that there is a setting which induces this behavior. It's tucked away into a small application called Image This application is ostensibly some sort of image importing application, but i've never seen it before. Among other things, it allows you to change the action to be performed when a "camera" device is plugged in. The setting is per-device, and you can opt to use any application (or no application). In theory you can even write your own complicated program to decide when to import, but for me the options and "No Application" are sufficient.

(Note: this is on Snow Leopard. If you don't have Snow Leopard, YMMV)