Do you ever notice how winter before New Year's looks different from winter after New Year's? True, the Christmas decorations are taken down sometime in January, but that's not exactly it. I could never really place it until a few days ago, when I saw a man in a stylish coat and scarf.
After the first of the year, we stop giving a shit about how we dress, because it's just too damn cold.
Before the first of the year, people are still excited about wearing their nice pea coat, a stylish scarf, and some sort of jaunty hat. But once January gets at full tilt, and all the way until March, it's like a race to see who can wear the most layers. This results in lumpy, waddling, sad-looking Minnesotans.
I don't think the fact that spring is just out of reach helps things much, either.
Showing posts with label the twin cities. Show all posts
Showing posts with label the twin cities. Show all posts
Saturday, February 13, 2010
Tuesday, November 3, 2009
Surly Darkness: The Max Fischer of Beers
I had a glass of Surly Darkness for the second time last night. I had had it once before and been truly unimpressed. But when our waitress came around and told us the non-"domestic" (don't get me started) beer selection and we heard "Surly Darkness," we all jumped and said "Yes! That one!" Including me. Even though I remember not caring for it.
And, once again, I had it and did not care for it. Because it is the Max Fischer of beers.
Surly Darkness could be good, but it tries to do too many things at once. I don't even know what flavors I'm supposed to be looking for or experiencing. It has so many things going on that not one of them is done well by my tongue. I'm not sure if it's supposed to be a hopstravaganza, if it's supposed to be like drinking a loaf of bread, or if it's supposed to have fruity/woody/spiced overtones. And I'm pretty sure the reason I can't tell is because it does all of these things at full tilt.
So, Max Fischer of beers, I'm not going to say you're bad. I'm just going to say I don't think you're good enough for me. But there are plenty of Margaret Yangs out there.
And, once again, I had it and did not care for it. Because it is the Max Fischer of beers.
Surly Darkness could be good, but it tries to do too many things at once. I don't even know what flavors I'm supposed to be looking for or experiencing. It has so many things going on that not one of them is done well by my tongue. I'm not sure if it's supposed to be a hopstravaganza, if it's supposed to be like drinking a loaf of bread, or if it's supposed to have fruity/woody/spiced overtones. And I'm pretty sure the reason I can't tell is because it does all of these things at full tilt.
So, Max Fischer of beers, I'm not going to say you're bad. I'm just going to say I don't think you're good enough for me. But there are plenty of Margaret Yangs out there.
Wednesday, October 21, 2009
Manlinest City
There has been a study commissioned by COMBOS, "the hearty, pretzel and cracker snack made with real cheese," to determine the manliest city in America. (Incidentally, I most closely associate with my sister, as she would always eat these on road trips when we were kids.) Minneapolis is ranked 18th. They've gotten everything wrong.
Their basic parameters of manliness are as follows:
Ostensibly, we are trying to measure the manliness of the men in these cities. Minneapolis may not be the number one manliest city, but let's measure based on some real manliness criteria:
Their basic parameters of manliness are as follows:
- Unhealth
- Banality of sports taste (NASCAR-related things were weighted more heavily)
Ostensibly, we are trying to measure the manliness of the men in these cities. Minneapolis may not be the number one manliest city, but let's measure based on some real manliness criteria:
- Number of beards, with extra points given for achieving the beard contest criteria.
- Total pounds of man-muscle
- Total pounds of beer belly
- Number of cars with flames on them
- Number of men shot in the chest by an anarchist who then go on to give their speech before being driven to the hospital
Monday, October 19, 2009
Let Me Explain Google Wave
Author's note: It's possible that you know all of this. I am writing this down in the hopes that people who didn't get it before might be enlightened by my thought process. Enjoy.
I sought out a Google Wave invitation, not exactly knowing what I was getting into. It was new and I wanted to add it to the list of new technologies I could claim myself as an early adopter of (the list, as I recall it, runs from mini disc to kindle--incidentally, neither lasted very long).
My invitation came on Friday night. I poked it a few times over the weekend, but it ran too slow and there was too much going on at once. I was a member of the Twin Cities Wave and pretty much no other waves. I was confused and I was bored.
(A wave is a message thread made up of individual messages called pings.)
Yesterday I was confused and bored again. But then I joined a few smaller waves with some friends.
Google Wave is the following existing technologies wrapped into one delicious web app burrito:
It may be obvious how there is some overlap with the functions the items on this list fulfill. But what was not immediately obvious to me is why it's so interesting to slip them all together into one very browser-crashing web application. Here's what I can see so far.
What it will be good for:
There is one problem I can see: the necessity of ubiquity. Sort of like Twitter, there's a critical mass that must be reached before this will be useful to me. I can't collaborate by myself. But give it a year; this thing will be pretty popular but, as I said, I don't think it will change the game on the scale of email.
I sought out a Google Wave invitation, not exactly knowing what I was getting into. It was new and I wanted to add it to the list of new technologies I could claim myself as an early adopter of (the list, as I recall it, runs from mini disc to kindle--incidentally, neither lasted very long).
My invitation came on Friday night. I poked it a few times over the weekend, but it ran too slow and there was too much going on at once. I was a member of the Twin Cities Wave and pretty much no other waves. I was confused and I was bored.
(A wave is a message thread made up of individual messages called pings.)
Yesterday I was confused and bored again. But then I joined a few smaller waves with some friends.
Google Wave is the following existing technologies wrapped into one delicious web app burrito:
- Wiki - Anyone can edit any part of a wave and there is a full record of who has done what. This beats wikipedia (or any other wiki I've used) by about a thousand in terms of intuitiveness.
- Message board - A ping (a message within a wave) can be replied to much like a LiveJournal or I Can Has Cheeseburger-style post, with root replies and sub-replies.
- Instant message client - Wave lets you see who is online. It is actually most like the old ICQ, where you can see what another person is typing as they type it. If you open up a wave with one other person--bam. Instant message.
- Email - It's not exactly like email, but it really helps to think of it as email: every message is private and includes only the recipients you choose. You can send a wave to a person when they're offline and it will sit in their inbox until they return.
It may be obvious how there is some overlap with the functions the items on this list fulfill. But what was not immediately obvious to me is why it's so interesting to slip them all together into one very browser-crashing web application. Here's what I can see so far.
What it will be good for:
- Collaboration - What I never could get wikis to do, Wave does almost effortlessly: one document with multiple editors. Google suggests you use Wave to have everyone at a meeting take notes; maybe smart, maybe dumb. The playback feature is key here--it totally trumps the edit history page on Wikipedia. Much more useful (to me) to see edits progress temporally than see them listed.
- Discussion - The problem with message boards is their public nature. The problem with email and Gmail is its linear nature. Wave lets you communicate privately in a message board setting. If you branch off into two topics, no more guessing what a person is replying to--you can create new waves based on old waves. Google Wave provides the sharpest, slickest format for private, lengthy online discussion so far.
There is one problem I can see: the necessity of ubiquity. Sort of like Twitter, there's a critical mass that must be reached before this will be useful to me. I can't collaborate by myself. But give it a year; this thing will be pretty popular but, as I said, I don't think it will change the game on the scale of email.
Tuesday, April 21, 2009
People Watching Backstory
I was sitting in Urban Bean this afternoon doing some work. I was unable to listen to music, because, like always, I had forgotten my one pair of headphones at work. This always makes for some great people watching.
Normally, the people watching gets up to a moderate level of interesting: I've seen cartoonists, graphic designers, study partners, couples fighting, and any number of lone laptop hunchers. I can generally figure out what's going on, more or less, and it generally seems pretty benign.
Today, however, I saw two people I couldn't quite figure out.
A man, maybe in his early or mid twenties, was sitting next to a woman somewhere between twice and three times his age. He was a husky build: not fat, exactly, but not lean. Even in his chair he seemed tall. His hair was cut short but was obviously thick. He was loud.
She was almost his exact opposite: She was meek in stature. She had fine, white hair in a pony tail. When she leaned over to speak to him I could not hear her--her mouth barely even opened.
They both pecked and squinted at laptops; the man's looked about 5 years old, the woman's looked about 10 years old. He shouted into a phone, giving an awkwardly large ramble of information to the person on the other side before asking if they had any studio or one bedroom apartments available. He was asking for openings immediately, or, failing that, the first of May. "I just moved to town and I need something as soon as possible." He made many of these calls, each time asking for the same standard information from people who want to sell it to him; yet, he remained uneasy and spoke quickly, tripping over his words at times.
They seemed to have only two qualifications: they need it cheap and they need it now.
Why don't they have a place to live? And where did them come from?
They don't have a place to live because they picked up and left where they were without a plan. The were in a hurry. Their only change of clothes was probably bought at Wal-Mart at 3am.
They are obviously lovers on the run. They came from Elsewhere--the town where her Old Man started asking too many questions. The man was almost insistent on giving his nonsuspiciously generic name before anything else: a little too eager to cement his new alias, perhaps.
Did they kill her Old Man? Or was he so scorned that he is after them with an ax? Whatever the reason, they fled to Minneapolis, a city small enough to be a less than obvious refuge, big enough to melt into the background.
And then he said "I'm going to MCTC this summer and my mom is going to cosign my lease."
A likely story.
Normally, the people watching gets up to a moderate level of interesting: I've seen cartoonists, graphic designers, study partners, couples fighting, and any number of lone laptop hunchers. I can generally figure out what's going on, more or less, and it generally seems pretty benign.
Today, however, I saw two people I couldn't quite figure out.
A man, maybe in his early or mid twenties, was sitting next to a woman somewhere between twice and three times his age. He was a husky build: not fat, exactly, but not lean. Even in his chair he seemed tall. His hair was cut short but was obviously thick. He was loud.
She was almost his exact opposite: She was meek in stature. She had fine, white hair in a pony tail. When she leaned over to speak to him I could not hear her--her mouth barely even opened.
They both pecked and squinted at laptops; the man's looked about 5 years old, the woman's looked about 10 years old. He shouted into a phone, giving an awkwardly large ramble of information to the person on the other side before asking if they had any studio or one bedroom apartments available. He was asking for openings immediately, or, failing that, the first of May. "I just moved to town and I need something as soon as possible." He made many of these calls, each time asking for the same standard information from people who want to sell it to him; yet, he remained uneasy and spoke quickly, tripping over his words at times.
They seemed to have only two qualifications: they need it cheap and they need it now.
Why don't they have a place to live? And where did them come from?
They don't have a place to live because they picked up and left where they were without a plan. The were in a hurry. Their only change of clothes was probably bought at Wal-Mart at 3am.
They are obviously lovers on the run. They came from Elsewhere--the town where her Old Man started asking too many questions. The man was almost insistent on giving his nonsuspiciously generic name before anything else: a little too eager to cement his new alias, perhaps.
Did they kill her Old Man? Or was he so scorned that he is after them with an ax? Whatever the reason, they fled to Minneapolis, a city small enough to be a less than obvious refuge, big enough to melt into the background.
And then he said "I'm going to MCTC this summer and my mom is going to cosign my lease."
A likely story.
Friday, February 27, 2009
The Case for #twincy, or: You Are All Wrong
There is a debate occurring, right now, on the popular social networking website Twitter Dot Com. The debate is over which hashtag is best for denoting tweets about the Twin Cities Metropolitan Area. After some discussion, it has come down to two contenders:
#twincy (represent!)
and
#msp (BOOOO!)
One of these is the correct hashtag, and one of these is an obvious lie. I submit to you that #msp is, in fact, the total travesty and abomination. There are many reasons for this:
Equity. The #msp hashtag is not equitable. It heavily favors St. Paul by allotting it two of three characters. However, #twincy places both cities on the same level, which is a positive step forward for regional equity and understanding.
Specificity. MSP is the three-letter designation for Minneapolis/St. Paul International Airport. If you use #msp as the hashtag for all Twin Cities-related tweets, how then will you differentiate tweets about the Minneapolis/St. Paul International Airport? This question remains unanswered. With #twincy there is no such problem.
Uniqueness. #msp could stand for just about anything. #my-sexy-pants, #many-sage-pimps, #minneapolis-saint-potato. Anything.
Further proof.
#twincy (represent!)
and
#msp (BOOOO!)
One of these is the correct hashtag, and one of these is an obvious lie. I submit to you that #msp is, in fact, the total travesty and abomination. There are many reasons for this:
Equity. The #msp hashtag is not equitable. It heavily favors St. Paul by allotting it two of three characters. However, #twincy places both cities on the same level, which is a positive step forward for regional equity and understanding.
Specificity. MSP is the three-letter designation for Minneapolis/St. Paul International Airport. If you use #msp as the hashtag for all Twin Cities-related tweets, how then will you differentiate tweets about the Minneapolis/St. Paul International Airport? This question remains unanswered. With #twincy there is no such problem.
Uniqueness. #msp could stand for just about anything. #my-sexy-pants, #many-sage-pimps, #minneapolis-saint-potato. Anything.
Further proof.
Subscribe to:
Posts (Atom)