23 October 2016

Layover 2

I'm in O'Hare on a layover and I'm in motion. I'm unrushed, having made my way through passport control with plenty of time to spare. I'm making my way to a flight to Seattle. The day seems bleak, the sky is grey, and the air is cold. I'm overtired. Walking through an airport can be an overstimulating experience: the people rushing around, the din of announcements. I feel disconnected from it all, moving steadily, the rush surrounding me.

I'm changing terminals. Boarding attendants are yelling and pointing down the crowded platform trying to maximize the number of bodies they can get onto the train that connects international arrivals and domestic departures. Standing on the train, I stop for the first time since I handed my paperwork to the border patrol agent.

As the doors are closing, a man runs through. The trains run every four minutes. There's really no need to do this, but that's the way this shit is done. If four minutes is really going to make a difference, the flight has, effectively, already been missed. There's no buffer for a slow person on a moving sidewalk, an unforeseen gate change, or a broken escalator.  It's the sort of thing that I sigh inwardly at, but move on from, because it's a pattern I see again and again. I'm still in my overtired fog, standing, facing the door, feeling little, saying nothing.

Now the doors are really really on the verge of closing. There's a clatter as a woman comes barreling through. The doors close on her arm and spring back open. It's loud, jarring, and unexpected. Words cannot express the momentary shock that I feel. The fog has vanished. With the doors reopened, she gets on the train

"That door closed on me," she says to her companion, the man who just made it through the door earlier. Her voice begins to take on more of an aggrieved tone, "You didn't have to get on this train!". The man brushes it off wordlessly, and fortunately an argument does not erupt.

But I wonder what it's like to be so determined, like the man, or feel so tethered, like the woman. Each of them had an opportunity to not get on that train and if they operated in a world where the most valued elements were order and safety, they wouldn't have. They both did though, and they did it together, though not without strife.

10 October 2016

Layover 1

I'm in Heathrow, sitting at the bar at a place called Huxley's. The place makes a big fuss about being British; celebrating modern British food. When the alternative is half a lobster and champagne for some princely sum, and I'm facing three more hours before a flight to Menorca, that seems just fine. When I approached the one remaining bar stool, the young man sitting adjacent gave a friendly look as he shifted his stool over to make room, but left his headphones in. He was not the only one with headphones in. Even the people without headphones are looking at their phones. I'm not.

I order a beer. A fast-talking guy, a speaker of Lithuanian as can be gleaned from the small badge of the Lithuanian flag on his nametag, assisted by two other guys, a colleague and trainee, both from India, provide efficient service, but are too busy to chat. The bar is L-shaped, and I'm sitting on the small side looking across towards the long end. Halfway down the long end, a young woman is passively rubbing her significant other's back with one hand, while in the other hand she holds her phone up to her face, giving it far more attention. At some point, the Lithuanian unsuccessfully tries to bum a smoke from his coworkers behind the bar. Unsuccessful, he heads to the kitchen and emerges with a cigarette behind his ear and leaves. I order another beer. The stool beside me opens up.

"Which of the beers has the most alcohol?" asks the 40-something American man who's sat down next to me of the trainee. The American, he's delayed, he's been at the airport awhile and will be for some longer, he announces, perhaps to bartender, perhaps to me.  The trainee doesn't know much about the beers and calls over his remaining colleague who runs through the list of lagers and ales on tap: unadventurous selections with a alcohol contents that, no lie, range only from 5.4% to 5.6%. The bartender suggests a slightly stronger Belgian beer in bottles, but the man, while he could imagine drinking said beer in a cafĂ© in Paris, decides he wants the strongest tap beer.

Something about the American makes me uneasy. There's a boisterous affability to his interactions with the staff, but it seems to be a mask over something: an angry volatility, a short fuse. Something feels like it's not going to end well. For awhile we're both silently drinking our beers.

"Is there a room or a dungeon or some place where I can smoke?" he asks the trainee.

"No..." the trainee softly intones, trailing off. I think the specification of a dungeon has thrown him. It's thrown me too. Dungeon? What the fuck? He riffs a little on the idea of a dungeon, talking a little about chains, taking things in a vaguely sexual direction. The trainee is still listening, but seems at a loss of words. The American seems almost apologetic on behalf of the trainee. His voice has conciliatory tone, as though he's fighting something back. "Can't do anything in an airport anymore. Fucking Muslims right?" The trainee gives an anxious grimace in response. Not ending well is starting. My second beer is soon finished, much faster than the first one. I eagerly pay and spend the rest of the layover sitting by the gate.


02 March 2016

Why I made a Seattle transit isochrone map generator

I made a Seattle transit isochrone map generator. You should check out this example of what it can do to fully understand what this post is about.


How do you use public transportation?

When I take the bus to work, I leave any time between 8 AM and 11 AM, more or less randomly. When I do leave, I don't check the bus schedule before I go. Once I've locked up the house, I'll put my work address into Google Maps and see which route it suggests I take. Then I'll double-check the real-time arrival times provided by OneBusAway as I start to walk to the stop, and potentially choose to reroute to another stop. When I leave work and go home, some time between 4 PM and 8 PM, I basically use the same strategy.

But that's not the only way I use public transportation. I'll go from my home in Wallingford to visit friends in Capitol Hill or the Central District using one or more buses. Sometimes I'll take a series of buses (and now a streetcar too) to Little Saigon to get produce, or a couple of buses (or potentially a bus and light rail) to get to a Grocery Outlet in Madrona or SODO for other sundries. Sometimes I'll use the bus to go directly from work to Georgetown to pick up brewing supplies and then head on home. I use public transportation to go pretty much anywhere.

For these other trips, even though they potentially involve making a connection between two different vehicles, I still do absolutely minimal planning. I rely on the public transportation system to be able to support a broad variety of largely spontaneously-timed trips and most of the time it works fine. I have a car, but outside of hiking trips, hauling building supplies and furniture, and larger grocery loads, I don't use it very often.

I think that many—perhaps even most—people do not use public transportation in this same way. Some people only rely on it to get to work, using peak-hour buses, or a ferry where there are only a few trips spaced at fairly infrequent intervals. They need to be ready by a certain time or wrap up work by a certain time in order to commute. They cannot use public transit in a spontaneous way. A lot of people are averse to transfers and only take public transportation to destinations that they can reach directly. That makes them car-dependent for a large number of trips.

I don't want to invalidate the needs or preferences of people who, for whatever reason, adhere to a rigid schedule or do not consider public transportation for all of their destinations. I don't want to say that I'm right and anyone who uses public transportation differently is wrong. But I do want to take the stand that if a public transit agency gives sole focus to these users, it will stagnate. It will serve well the people who already use it, but it will not induce people to use it for anything other than their pre-scheduled trips. In my mind, effective public transit should challenge people to view their cars as an optional convenience rather than the only thing that brings them travel flexibility. After all, if the transit network serves spontaneous trips all over the city well, it serve schedule adherents or more-than-occasional drivers just as well.

The way I use public transportation does not answer the question of why I made a Seattle transit isochrone map generator. An isochrone map generator is not really useful for deciding what bus to take on a given day. The tools for that already exist. This is a different sort of tool.


I've lived in Seattle for about four and a half years. I've been using public transit all that time. For reasons I can't fully explain, I don't just find public transportation useful but intrinsically neat and interesting.  But only recently have I gotten interested in public transit policy. I think part of that distinction is that a public transit network can seem like a static thing most of the time. Sure there have been frequency cuts and a subsequent frequency buy-back by the city, but most of the time the routes don't change very much. However, a recent set of changes known as Link Connections grabbed my attention.

For those outside of Seattle, or those who value their time enough not to follow the intrigue of transit policy, here's a brief rundown of public transit in Seattle. Bus service in Seattle is operated by King County Metro, which operates bus service for all of King County. King County Metro operates a variety of route types: point-to-point routes within the city of Seattle, peak-hour express routes designed to get commuters in and out of the city from the suburbs, and less frequent point-to-point routes outside of the city. The other big player in the region is Sound Transit. Sound Transit is a three county agency with jurisdiction in King County, Snohomish County to the north, and Pierce County to the south. Sound Transit operates longer-range commuter buses, but is best known for the its light rail line, called the Link, that runs from SeaTac Airport to downtown Seattle. In mid March, Sound Transit will open an extension that provides stations in Capitol Hill and the southeastern edge of the University of Washington campus.

Link Connections is King County Metro's attempt to better synchronize its network with the new frequent, reliable light rail service that will exist between the university, Capitol Hill, and downtown. The idea is that some bus routes that once went between or near the stations on their way downtown can be truncated at these stations. Riders can continue to their final destinations on the light rail. Even with the transfer, the hope is that operating part of the trip in a grade-separated vehicle with fewer stops will make the trip faster than the former one-seat ride.

Link Connections started with King County Metro publishing two plans for route restructures, known as Alternative 1 and Alternative 2. Alternative 1 was a pretty radical restructure. It redirected almost every route in Capitol Hill to serve the light rail station, it greatly reduced the bus capacity between downtown and Capitol Hill in anticipation of most riders using the light rail between those two locations. This had the benefit of giving many routes frequencies better than 15 minutes midday and under 10 minutes at peak times. In northeast Seattle it reduced to peak-only service many routes that connected neighborhoods to downtown, truncated many all-day routes at the light rail station, and consolidated some routes on parallel paths into single corridors with 15 minute frequencies rather than half-hour ones. Alternative 2 was far less ambitious. It terminated fewer routes at the light rail stations and generally made fewer consolidations and modifications.

Around this time, I started reading the Seattle Transit Blog and had been turned on to several talks by transit consultant Jarrett Walker. Many of the Seattle Transit Blog authors and commenters seemed to like Alternative 1. It also created a network more resembling a grid and created new high frequency corridors where few existed before. The more I thought about it, the more Alternative 1 seemed like a really inspired and forward-thinking set of changes. It made a lot of sense to me because it was extremely compatible with the way that I use public transportation. Higher frequency would mean that even if I arrived at the bus stop at the least optimal time, the bus would arrive sooner and I'll ultimately get to my destination earlier. A more grid-like network, less focused on shuttling people downtown, would better meet my desire to get anywhere in the city within a reasonable amount of time.

Alternative 1 was not without problems. Many questioned the feasibility of transfers at the University of Washington station as few buses actually stopped directly at it. There was a fear that combining certain segments of routes would hurt the reliability of currently-reliable routes. A community group was rumored to be fighting the decision that buses would no longer collectively traverse the full length of Madison Street. Some felt as though the consolidation of corridors was done without respect to the hilly geography of Capitol Hill.

As straightforward as the aims of Alternative 1 and Alternative 2 seemed, the followup plans seemed increasingly confused and reactionary. An Alternative 3 largely held the Alternative 1 line in northeast Seattle, but restructured the Capitol Hill routes in strange ways, some seemingly antithetical to the goal of connecting adjacent neighborhoods to the light rail. A subsequent proposal rolled back many of these changes, in the process restoring much of the bus capacity between downtown and Capitol Hill and making several routes take a bizarre detour onto Madison Street. This proposal was submitted to the King County Council, which holds final authority on any large restructures. The chair of the transportation committee, citing community concerns, restored, in reduced capacity, two routes that had been cut in every previous plan. This further diluted the goal of consolidation, as the operating budget for these restored routes would ultimately have to come out of capacity allocated for the new consolidated routes. After approval, the planned Madison Street deviation was found to include a turn too tight for a bus to make, forcing its elimination. A later administrative change moved an additional route in Capitol Hill closer to the station. By the time everything was agreed upon, northeast Seattle resembled Alternative 1 with a couple of artifacts from the current service pattern and Capitol Hill received changes that were only slightly more ambitious than the original Alternative 2.

I felt frustrated by this. It seemed as though a well-formed plan had been watered down by well-meaning but loss-averse citizens, community groups, and politicians. It seemed as though, in the face of criticism, King County Metro had acquiesced to demands rather than responding with data to criticism rooted in anecdotes. Reading some of the comments on Seattle Transit Blog posts, I did not feel alone in this feeling of frustration and loss. What I observed among some Alternative 1 proponents was a sense of cynicism that attributed these modifications to "politics". That didn't sit well with me. Blaming "politics" seemed cheap and simplistic, falling back to the cliché of government as a blundering bureaucracy. It invalidated the positions of the individual people who felt a sense of concern and loss by the restructure and argued for modifications. As right as I felt about Alternative 1 being a better solution, I did not feel as though I was in a position that I knew enough to invalidate anyone's feelings.

While these changes were in flight, I was giving a lot of thought to how I would restructure the Capitol Hill network. I set the goals of being sensitive the hilly nature of the region,  minimizing cases where riders would need to start by going in one direction to ultimately go in the opposite direction, and holding a hard line on only running minimal capacity on paths that were well-served by the light rail. As I started drawing these networks, I realized that I had a big problem.

Even if I could draw what I envisioned to be the perfect network, I had no way to convince myself that it would actually be better in practice. Just drawing lines on a map and calculating reasonable frequencies given the existing amounts of bus service would give me an idea of this, but no concrete proof. Furthermore, if I were to propose it as a viable solution, I would not actually be demonstrating its value to skeptical observers. I would be susceptible to the same sort of commentary that, in my mind, undermined Alternative 1. I could argue that it was more grid-like and connected many neighborhoods to high frequency routes. But, when a bus route is targeted for elimination, those reasons are unlikely to resonate with people who have a bus that they consider their bus and take every day. There's so much ambiguity and very little interactivity in the typical transit map. Sure different line styles can show frequency characteristics, but having to reason about transfers with such a map requires a full timetable. Evaluating such a restructure becomes a burden to the rider, who just knows that their existing bus works well enough. 

One day, though, I was sent a video of a presentation where Jarrett Walker used an isochrone map to support a line of explanation that these sort of maps demonstrate the amount of "freedom" that a public transit network provides. That immediately resonated with me. First, it perfectly described how I use transit. I don't have set routes, so just looking at routes doesn't allow me to analyze the utility I'd get out of a transit network. Meanwhile, an isochrone map shows an abstracted view that emphasizes the extent of the network, something that is immensely useful to me.

It also raised a question about how I felt about the demise of Alternative 1. Was King County Metro's failure to implement Alternative 1 not a failure of "politics", but a data visualization problem? King County Metro's documentation on the Link Connections restructure was a collection of route maps and high level explanations of which alternate routes to use in the event that one's chosen route was on the chopping block. However, these documents were failing to answer a very critical question, if my bus goes away, can I still reach the set of places that I need to go in about the same amount of time as I could before? If a concerned citizen could consider two isochrone maps centered at their home, one of the previous transit system and the other of a proposed replacement, and check that their destinations were in the same or lower time band as before, wouldn't that be more convincing than route lines on a map? Consequently, if the isochrone map showed a marked degradation, that person could raise a well-reasoned, rather than reactionary, complaint. The agency could then consider if the network was wrong to begin with or if improvements to everyone else outweighed this case and something like carpools, an on-demand shuttle, or taxi fare reimbursements could be used as mitigation for the impacted region.

So I started programming an isochrone map generator over the course of a couple of months, grabbing time after work and on weekends. I used King County Metro's Generic Transit Feed Specification files for schedule data and the Google Distance Matrix API for walking distances. The algorithm itself is a fairly basic recursive one, but I spent plenty of time screwing it up. Considerable time also went into performance profiling. Originally, I would leave it overnight to compute a map for one specific time period; now it can compute a full days worth of 30-minute travel maps in a little over 5 minutes. I found out later there are other isochrone map generators out there from WalkScore and Mapnificent, but, while being quality realtime products that run circles around my comparatively pokey generator, they make simplifying assumptions or don't reveal enough about their methodology to feel comfortable abandoning my own project.

I would assume the transit planners at King County Metro have far better tools than what I can program in my spare time. So I'm surprised that the transit planners employed by the agency, who judging from Alternative 1, appear extremely competent and daring, either don't have the tools to generate isochrone maps or don't believe they'll be an effective tool to convince the public of the efficacy of the route systems they've designed. I would love to know what the actual case is. I'm only one data point, but it is something I'd find useful to see.

While the maps are a good visualization tool, they still must be interpreted subjectively. When condensed further, I think they can provide a very useful piece of data. Taking a starting point and simply counting the number of points that can be reached from that point can serve as a naive score for the transit network at that starting point. Choosing a set of randomly selected but geographically diverse points can serve as an overall network score. The score can be refined further by weighting points for their access to jobs, culture, retail, and social services. That way, when a plan is presented, it has an objective measurement, as well as compelling visuals that can back up the merit of the score.

I think using isochrone maps as a core component of transit planning has the potential to invert what is currently a process that seems like it must be frustrating to all sides. Currently, the process appears to work by first having transit planners design a network using some unknown mechanism to evaluate it. Then route maps are revealed to transit riders and community groups, who, looking at any elimination, may doubt that the transit planners understand what is important to them. They suggest changes either directly or by way of insisting the county council amend the plan. As frustrating as those revisions were to me in the case of Link Connections, I firmly believe the public must be involved in the process in a meaningful way. After all, public transportation is financed by, and more importantly is intended to serve, the people. Imagine a process where transit riders and community groups define what the high-level goals of the transit network are—what, in the abstract, are the most important things for it to serve. The politicians on the council can debate and consolidate these goals into publicized, fixed weights. Then transit planners can redraw networks without fear of later meddling, provided they increase the score of the transit network. If people are subsequently unhappy with the transit network, they can evaluate whether the transit planners did not score the network honestly or if the scoring system itself needs work. Everyone has an important role that maximizes their strengths and minimizes their biases. There's no possibility, or even the perception of the possibility, that a rogue transit planner can neglect residents in a given area or that the committee chair can drawing a line on a map to appease a voting bloc.

When I present the idea of a system based around a numeric score, one thing that I worry about is that  is that it will be perceived as inherently harsh and unfeeling. Data-driven processes, at their worst, can be ham-fisted and alienating; I've been on the other side of them. Nonetheless, I feel as though there is an ability in scoring to make less biased decisions. When I was trying to draw a new alternative for Link Connections in Capitol Hill, I was thinking about what could work for me. I try to be aware of what characteristics I have that shape the way I view and exist in the world: I'm male, fairly young, white, and without any mobility or uncorrectable vision impairments. I can climb hills, walk quickly, and run to make a bus. I can stand around at a bus stop at night with little fear of harassment or attack. No one is going to call the cops if I'm walking through their neighborhood. By encoding the restrictions that people face in their lives as selectable parameters in the map generation software, an isochrone map can show a transit planner in a clear way, what the transit network looks like from another person's point of view.

I want to improve my software so that it can make maps that halve the standard walk speed, or not permit transfers after a certain time, or impose a maximum walking distance. Scores can be generated for a transit network given each of these restrictions and factored into a larger composite score. So at this point while I have made a Seattle transit isochrone map generator, I need help to make it into a tool that can actually effect change. I need one question answered, from a diverse set of people, in order to figure out where to go from here:

How do you use public transportation?

23 January 2016

Pokemon glitch and Built to Spill videos of the week: Foundational Importance

There are three types of people in the world. The first type are people who, by either generational difference or  general lack of interest, know nothing about Pokemon at all. The second are familiar with Pokemon. The third are "Pokemon people". Pokemon people are like above average drivers: there are many more claimants than actual members of the group. Unlike being an above average driver, being a Pokemon person is not, in truth, a really a desirable social status. You can recognize a Pokemon person when they enter a conversation wherein type two people are referencing Pokemon in some superficial or nostalgic way. A Pokemon person will derail the conversation with details of the glorious couple months when they were an operator in a Pokemon-related IRC channel. Pokemon people necessarily know the controversy surrounding Blizzard's freeze rate. The second type of people can probably parse the aforementioned sentence, but are baffled by the implications. The first type of people have skipped to the Built to Spill video or more likely stopped reading all together.

All this is relevant because the following glitch video touches on something so iconic that it's likely, in my mind, that a type two person would recognize it entirely.

Pokemon Blue - Missingno. and 255 Mewtwo! (video by TheCheatMaster) HORRIBLE TECHNO WARNING: MUTE RECOMMENDED
This is the item duplication/over level 100 Pokemon/MissingNo. glitch. I think it's sort of unusual for a game to have a well known glitch. Maybe I'm overstating the well knownedness, but this is the type of thing that I'd expect anyone who played classic Pokemon to be aware of.  It has a a Wikipedia page. This glitch is so well known that it's hard to find a good Youtube treatment of it. It's just that ordinary. There are more videos of people sitting near the backs of buses and recording the engine sound.*

I'm sort of fascinated by the epidemiology of this glitch. I remember being a young kid in my parents' basement watching my friends playing Pokemon. I was reluctant to play it; it seemed like a really popular fad and I avoided such things with pathological zeal. But on this day I was testing the waters a little bit and asked my friend what Pokemon he was using as he slew his opponent's Pokemon with what appeared to a garbled collection of pixels. He said it wasn't really a Pokemon, but a glitch.

This sorta blew my mind. How did this glitch exist so stably within the game?  What was it meant to be? Was this cheating? How'd he figure out how to get it? This was in the days where the internet was something used primarily by academics and accessed via modems. This thing spread kid to kid, the old fashioned way.

A couple months later I started playing Pokemon, deciding that it was actually quite a compelling game, and got pretty deep into it. I was reluctant to perform this glitch; I had decided that it was cheating and I would not do such things. Nonetheless, I was fascinated with it. There seemed be an aesthetic rightness to it, almost a sense of intentionality. Yeah, you were performing a set of seemingly arbitrary actions but there was a sense of balance to it. You might encounter MissingNo. and get a huge number of your sixth item, but you could also encounter some extremely high level Pokemon and get mauled by it. There was reward, but it was coupled with risk.

I theorized about this glitch. Based off of the experiences of my friends it seemed as though you would encounter either MissingNo., a nearly identical glitch in which the only decipherable characters were 'M, either an Electrode or Magnemite at some level over 100 depending on whether you had Pokemon red or blue, and an arbitrary Pokemon over level 100 that seemed locked to the specific cartridge. My friends didn't really share my interest in this speculation, but were more keen on duplicating Masterballs to catch Pokemon and Rare Candies to level them up.

My interest in Pokemon waned over time, but the changes in the times conspired to reverse that. When my parents upgraded from dialup to cable, I found myself exposed to an abundance of information about all facets of Pokemon and my interest in it was rekindled. I found my theories, as logical as they seemed, to be invalidated. Those over level 100 Pokemon, and MissingNo., and 'M were determined solely by the trainer name. Namely, the second and third, fourth and fifth, and sixth and seventh characters formed pairs that got interpreted as a level and Pokemon, respectively. My friends, named Brian, Jon, Allan, and Jason, all had Ns at one of those critical locations. Only Allan had the blue vesion, and coincidently happened to use lowercase characters to spell his name. Of course, the uppercase N corresponded to the identifier for Electrode and lowercase N corresponded to Magnemite. The other characters corresponded to the other Pokemon and MissingNo.s. The character signaling the end of the name created 'Ms.

That sated my curiosity, but only partially. Why one would encounter MissingNo. was no longer mysterious, but the nature of it continued to be strange. Why did just encountering it duplicate the 6th item? Why were its stats and moves so weird? Those mysteries were not resolved until much later. They're fairly interesting, but in the Pokemon glitch narrative, where each glitch builds upon an earlier glitch to enable future game manipulation, the whys of MissingNo are not actually not that important. It turns out the most important element of the glitch is the fact that MissingNo. increases the amount of the 6th item by 128. While my childhood friends had their Masterballs and Rare Candies, future glitches depend on its ability to create arbitrary amounts of any item. But why that's important is a topic for another week.

Built To Spill - The First Song - Philadelphia, PA - 11/2/2013 (video by noochnooch)
MissingNo. is well known, this song probably not so much. MissingNo. is the first of a series of Pokemon glitches, in a way, and this is the first song off the first Built to Spill album, and it's called The First Song. The connection is tenuous, but I absolutely love this song. I think I was looking for a decent quality full Built to Spill live show to have in the background while working and came across this show in Philadelphia. This was the first song of the set and I was utterly transfixed by the introduction. It took me awhile to place it, and I definitely listen to The First Song, and its containing album Ultimate Alternatives Waivers as a whole much more often now. All I can say is "Aw thanks".

Part of what I like about this performance is that the band takes a song that on the album seems like a bunch of guitar parts spliced together, sometimes rather roughly, and performs it lives with what seems like effortless coordination between the performers. I also like that the song is about difficulty about being able to express ideas through language, and by reading this, you are painfully aware of how strongly this resonates with me.

https://youtu.be/d2ZVDzq-iPw is a reasonable starting point

09 January 2016

Pokemon glitch and Built to Spill videos of the week

I posted this on thefacebook.com the other day:

when people tell me they'd be bored if they didn't have a job to do, i don't really get what they're saying because i think could fill a whole lifetime using youtube to watch old built to spill concerts and pokemon glitch videos

And I don't think it's totally untrue. It's an exaggeration, sure; I'd probably need a little more than Built to Spill concerts and Pokemon glitch videos for whatever a well-lived life is, but there's a lot of material there! So in my ongoing quest for complete self-destruction I'm about to take some things I enjoy, and turn them into an obligation. This has had decidedly mixed results in the past, as I recline with an abundance of comforts bourn of employment in a booming field, while simultaneously not looking forward to an upcoming week at work where I'll have to wake up in the middle of the night if some dumb computer shit* breaks.

So why not post weekly Pokemon glitch and Built to Spill videos on this very website?

Pokemon Blue: Memory/ASM hack - The game is memory hacking itself! (posted by TheZZAZZGlitch)
I don't think this is what people think of when they hear "Pokemon glitch". First of all, there's no setup. In this video you're diving right into a world that's falling apart before your eyes. There's also no reward. Mew is not walking through that door. You don't talk to the Old Man, surf up and down the coast of Cinnabar Island, and encounter a MissingNo because it's represents a neat confluence of programming mishaps; you do it because you want 128 more Master Balls. Right?

That's not entirely true in my mind. What's neat about a glitch can be that it rips away the abstraction that the game is some world unto itself, and exposes it is a fallible creation where everything you see and do is just data getting interpreted and changed. From that perspective, a truly pure glitch doesn't get you stacks of Master Balls or lets you catch Mew, it reminds you that Master Balls are fake and Mew is dumb computer shit.

This glitch video is basically as pure as it gets.  A small program is injected into the game and hooked into a timer so randomly generated byte in memory is changed. What's neat about this is that the effects can be subtle or huge. A single pixel could shift, a name could get corrupted, the mechanics of a battle could be completely destroyed, or the game could just crash. Greater is that the effects can compound. Perhaps the changed byte just results in changing the color of a single tile. That won't have a great deal of impact. But if that byte falls in executable code or changes the interpretation of some data, further unanticipated effects could occur from that single modification. This cycle could continue and continue. The smallest perturbation can spiral out of control in totally unpredictable ways. Also these perturbations are occurring every 50 milliseconds.

What's even more neat about this is that while the video shows the game being run in an emulator on a computer, it's conceivable that this could be done using just a game, a Gameboy, and an abundance of time. Through the dedicated work of people stacking small glitch upon small glitch, it has been found that Pokemon basically allows arbitrary code to be executed. You can create an entirely new game. How's that for ripping away the abstraction?

For the record, my favorite part of the video starts around 11:06. Things seem to be going pretty well, with a couple of minor graphical glitches until the music ominously slows down. Then a battle ensures. As Safari Zone battle decorum goes totally out the window, the music seems to tear itself apart and the screens fills with layers and layers of misplaced tiles. Horror movie stuff.

Built To Spill - Conventional Wisdom (Live in Sydney) | Moshcam (posted by Moshcam)
If you're expecting the same level of detail of explanation as the previous video, you're out of luck. It's weird, but I've been fascinated by Pokemon glitches for far longer than I've even actively sought to listen to music, much less came to appreciate Built to Spill, much less watched a shit ton of Built to Spill concert videos on Youtube. So the response here is less developed, more visceral.

I don't even know how I ended up watching this video; I think it was in a playlist. I think Conventional Wisdom is a pretty blah Built to Spill song. It's totally listenable, but not something I'd seek out a concert video of. But, I was listening anyway and during the instrumental part at the end something sounded really, really familiar. It took me awhile to place it and I had my doubts at first, but then I realized the instrumental there interpolates parts of Shit Brown Eyes from the Built to Spill Caustic Resin EP. Pretty obscure stuff, thrown out there where you least expect to find it, a one-off ad-lib in a performance of a song written some 11 years later. Sometimes life surprises, indeed. 

*It's really useful to some people! But anything technological that wakes you up in the middle of night is totally dumb computer shit then and there.