It’s Black Friday, and the season of consumerism will be upon us, and the race to Christmas Day will dominate our lives. The holidays are a time of giving, a time of faith and tradition, a time of family and togetherness and celebration. But with the mad shopping dash to buy Christmas gifts, it’ll also be a season of stress, financial anxiety, and even debt. It’ll be the most significant contribution of the year to the coffers of huge retail conglomerates who hoard wealth, monopolize markets, and prey on consumers and their workers.
This line of thinking is nothing novel or new, but it’s especially on my mind with my involvement with the OccupyMovement. And whether you’re bothered by billionaires or not, I hope there’s something we can all more or less agree on, which is:
Sam Adams, the Mayor of Portland, had given the Occupy Portland encampment at Chapman and Lownsdale parks three days’ notice of eviction. “At 12:01 am on Sunday, November 13, all persons and property in Lownsdale and Chapman Squares will again be subject to enforcement of all laws including the laws against being in a park after midnight (PCC 20.12.210), and erecting structures in a park (PCC 20.12.080),” Adams said, and added that “on or after November 13” the parks would close for repair.
Occupy Portland was torn. Some seemed to agree with Adams’ reasons—that the camp had become unsafe, unsanitary, a mire of squabbles and drug use. They advocated abandoning the camp and leaving camps behind, to focus on other strategies. Others thought the eviction would at least be an opportunity to “clean house” and make a fresh start with a new encampment. And many were determined to hold the camp at all costs, seeing eviction as a quashing of the movement.
As I studied all these viewpoints, I was torn myself. Processing with my head and not my heart, I could see logic in all perspectives, and having only slight, surface experience with the encampments I didn’t have a lot of hard data on how well it functioned and whether or not it served a purpose for the movement. Occupy Portland put out a call for all citizens of Portland, as well as brother and sister protesters in Seattle, to come rally at the midnight deadline to stand together against the eviction. My head was torn, but my heart was telling me to be there.
Ever since my initial exposure to Occupy Wall Street, I’ve longed to participate. The Occupy Portland branch has been thriving, but living outside the city on a St Helens farm, and temporarily without transportation, there was little I could do but watch.
So watch I did! I followed the #OccupyPortland and #OccupyWallStreet Twitter streams, read dozens of articles as they popped up daily, viewed scores of Youtube clips, and watched demonstrations on Livestream when I could. When protesters chose to sit down and be arrested in Portland’s Jamison Square, my heart longed to be with them. So I held vigil, watching until the last protester was arrested at 3:30 in the morning, livetweeting quotes from the Occupy Portland Livestream. I spread links across Twitter, Facebook and Google+. I traded thoughtful Tweets with Portland Mayor Sam Adams. But I had not set foot in the Occupy Portland encampment, or walked bodily among them in their numerous marches.
When I was young my brothers and I had a Commodore 64 Personal Computer. We all three of us sat enthralled for many hours by the vast trove of video games available for the machine, but I wanted more. I wanted to create. I wanted to get under the hood of this 64K, 16 color processor that could display 8 sprites—8! onscreen at any given time. I wanted to unlock its secrets and make games myself.
I had no teacher. I didn’t know any computer programmers, and there was no school curriculum for it. All I had to guide me was my Commodore 64 User Manual and my own determination. I started writing simple programs in BASIC, gradually increasing the complexity until I could build something that almost resembled a playable computer game.
But there was always an obstacle. The documentation was spotty; there were several BASIC commands in the manual that simply did not work when I input them as shown. I checked out books from the library, but they were unclear on some key concepts; I could input a mass of command lines and they would function as the book described, but I couldn’t pluck out the principle behind them that would enable me to use the techniques myself, spontaneously.