I know this link is making the rounds again, but if you haven't seen Stephen Colbert beating the crap out of everything Washington - you really should.
Stephen Colbert rips Washington a new one.
(It's the full C-SPAN footage) You'll need to jump ahead to 51 minutes into the program.
Righteous.
Tuesday, April 24, 2007
Friday, April 20, 2007
Hijacking the Superbowl
This story is pretty damn funny...
MIAMI, FL (PRWeb) -- Just days after the Boston bomb scare, another team of Boston-based pranksters smuggled and distributed 2,350 suspicious light-up devices into the Super Bowl. Due to its attractiveness as a terrorist target, Dolphin Stadium was on a Level One security alert, a level usually reserved for Presidential inaugurations. By posing as media reporters, the pranksters were able to navigate 95 boxes through federal marshals, Homeland Security agents, bomb squads, police dogs, and a five-ton X-ray crane.Yeah, they're shamless self promoters, but they're still pretty damn funny.
During the second quarter of the Super Bowl, the team of pranksters -- who call themselves the "Super Six" -- quietly distributed thousands of "Prince Party Packs" to an entire section of Dolphin Stadium. Each packet contained a light-up necklace with official-looking instructions. By turning on the necklace lights during the halftime show, Super Bowl fans believed they would be spelling out the word "PRINCE."
But they didn't. They spelled a secret message that was broadcast to 93.1 million people.
Thursday, April 19, 2007
Ahh nature....
Umm....
Mr. duck....?
...mind getting the hell outta my back yard?
Mr. duck....?
...mind getting the hell outta my back yard?
(just a visual from the other day's excitement...)
Wednesday, April 18, 2007
Number to beat
I'm a news junkie, always have been.
I want to be plugged in. It's never been enough to know the latest news, but to find multiple accounts of the same event - then look for the different granules of information they are based on. This pastime has become less enjoyable in recent years - as the news has (at least in my opinion) turned considerably darker. I'm finding myself so put off by traditional mass media that I find myself tuning out more and more.
This is where I'm at with Virginia Tech. Not that this story is unworthy of attention - it's just that I am sick to death of the kind of attention it is receiving.
We've seen this movie before.
---
Start with a place at random: Littleton... Springfield... Blacksburg.
At first, the media just does its job.
Tell us what happened/is happening.
Not long after this phase, things start to go wrong.
Video is obtained. Solemn newscasters caution it may be disturbing, and then play it on an endless loop next to talking head interviews.
Eyewitnesses are found and interviewed live. Newscasters inch their questions towards painful subjects: "Did you see the shooter?" "Did you know the victims?" and finally "Did you personally see anyone shot"
Tell us about the blood.
Frequently, the eyewitness will become upset. The interviewer will visibly show their concern, "How are you holding up?" "Tell us how you are feeling," "How are you dealing with this?"
Are you scared? Are you in pain?
Early reports will have come in - they will be wrong.
The shooter is dead. The shooter is at large.
Ten are dead. Twenty. Less than twenty. More.
Possibilities abound, and are trotted out one after another by speculative journalists who aim to point out that the event may be even worse than first thought.
The carnage is tallied. The networks wring their hands and dispatch live crews, because modern media has conditioned us to expect that the person reading copy off a teleprompter must have a backdrop that is both live and relevant.
The police hold a press conference. It serves to dispel the more sensational possibilities we have been offered by the news. The shooter is dead. We learn the identity of the shooter, the true number of victims.
We learn, to our horror - the 'What' and the 'How.'
The facts established. The chorus of 'whys' can now begin:
"Why here?" "Why did they do this?"
We delve into the recent history of the shooter. "Where did they live?" "What did people think of them?" "What was behind their rage?"
There is a why. Tell us what it is.
These questions only serve as filler while bios of the known victims can be assembled and edited. We are shown grieving family members, survivors in tears.
Experts in grief counseling arrive in the form of talking heads. "What is this community going through?" "Tell us what you've heard from the families."
Pain. Show us the pain.
Recriminations, previously thought unseemly, become acceptable. The police were too slow. This should have been prevented. Lessened. It didn't have to be this bad.
Someone is to blame.
In a natural segue, the news shifts to "How do we stop the next shooter?" Criminologists, law-enforcement officials, and politicians spend ever-increasing amounts of time telling us the same thing:
Disturbed people who have easy access to firearms can hurt lots of people before we can stop them.
We cannot stop this.
---
All of this - all of the horror - is recorded and broadcast into living rooms, dorm rooms, workstations, bus stations, cars, bars, coffee shops, restaurants, every-frickingwhere -
-even some dimly lit basement where some man (and it is always a man) stops to watch. They see suffering on a national scale. The “worst ever,” they hear, over and over. Powerless, angry, they reflect on their wounds and those they hold responsible.
Then they think:
32. Yeah. I can beat that.
I want to be plugged in. It's never been enough to know the latest news, but to find multiple accounts of the same event - then look for the different granules of information they are based on. This pastime has become less enjoyable in recent years - as the news has (at least in my opinion) turned considerably darker. I'm finding myself so put off by traditional mass media that I find myself tuning out more and more.
This is where I'm at with Virginia Tech. Not that this story is unworthy of attention - it's just that I am sick to death of the kind of attention it is receiving.
We've seen this movie before.
---
Start with a place at random: Littleton... Springfield... Blacksburg.
At first, the media just does its job.
Tell us what happened/is happening.
Not long after this phase, things start to go wrong.
Video is obtained. Solemn newscasters caution it may be disturbing, and then play it on an endless loop next to talking head interviews.
Eyewitnesses are found and interviewed live. Newscasters inch their questions towards painful subjects: "Did you see the shooter?" "Did you know the victims?" and finally "Did you personally see anyone shot"
Tell us about the blood.
Frequently, the eyewitness will become upset. The interviewer will visibly show their concern, "How are you holding up?" "Tell us how you are feeling," "How are you dealing with this?"
Are you scared? Are you in pain?
Early reports will have come in - they will be wrong.
The shooter is dead. The shooter is at large.
Ten are dead. Twenty. Less than twenty. More.
Possibilities abound, and are trotted out one after another by speculative journalists who aim to point out that the event may be even worse than first thought.
The carnage is tallied. The networks wring their hands and dispatch live crews, because modern media has conditioned us to expect that the person reading copy off a teleprompter must have a backdrop that is both live and relevant.
The police hold a press conference. It serves to dispel the more sensational possibilities we have been offered by the news. The shooter is dead. We learn the identity of the shooter, the true number of victims.
We learn, to our horror - the 'What' and the 'How.'
The facts established. The chorus of 'whys' can now begin:
"Why here?" "Why did they do this?"
We delve into the recent history of the shooter. "Where did they live?" "What did people think of them?" "What was behind their rage?"
There is a why. Tell us what it is.
These questions only serve as filler while bios of the known victims can be assembled and edited. We are shown grieving family members, survivors in tears.
Experts in grief counseling arrive in the form of talking heads. "What is this community going through?" "Tell us what you've heard from the families."
Pain. Show us the pain.
Recriminations, previously thought unseemly, become acceptable. The police were too slow. This should have been prevented. Lessened. It didn't have to be this bad.
Someone is to blame.
In a natural segue, the news shifts to "How do we stop the next shooter?" Criminologists, law-enforcement officials, and politicians spend ever-increasing amounts of time telling us the same thing:
Disturbed people who have easy access to firearms can hurt lots of people before we can stop them.
We cannot stop this.
---
All of this - all of the horror - is recorded and broadcast into living rooms, dorm rooms, workstations, bus stations, cars, bars, coffee shops, restaurants, every-frickingwhere -
-even some dimly lit basement where some man (and it is always a man) stops to watch. They see suffering on a national scale. The “worst ever,” they hear, over and over. Powerless, angry, they reflect on their wounds and those they hold responsible.
Then they think:
32. Yeah. I can beat that.
Tuesday, April 17, 2007
Wednesday, April 11, 2007
You gotta be freaking kidding me...
Watching the current administration read from the same scandal script can get tiresome.
As Glenn Greenwald pointed out the pattern has been:
In the recent Gonzalez brew up - we've learned that White House staffers have been using email accounts sponsored by the Republican National Committee. Why would they do that? Because RNC communications aren't subject to open records requests, as they aren't government documents.
Unfortunately for the White House, this tactic will protect them from the curious citizen or watchdog group, but not a Congressional investigation. The White House can't claim executive privilege, since these are political communications.
At this point, those in the administration realize they are off the script - so they improvise-
(From the AP via TalkingPointsMemo)
I'm hoping a group of forensic computer specialists tear these idiots a new one.
As Glenn Greenwald pointed out the pattern has been:
1. Questions about administration conduct are raised.So, now that the White House is facing a hostile Congress. The game plan doesn't work so well.
2. Administration denies wrongdoing.
3. Administration officials selectively and voluntarily disclose exculpatory documents, appear before Congress, assure everyone that safeguards are in place, deny wrongdoing, and claim the conduct in question is used only for proper purposes (e.g., protecting country again terrorism).
4. Administration followers -- led by those controlling Congress -- insist that no investigation is needed because Official X made clear that there are safeguards in place protecting us and everything is being done for proper purposes.
5. Congressional Republicans block Congressional investigations, compel no disclosure of evidence, do nothing to investigate administration claims.
6.Scandal ends, unresolved.
In the recent Gonzalez brew up - we've learned that White House staffers have been using email accounts sponsored by the Republican National Committee. Why would they do that? Because RNC communications aren't subject to open records requests, as they aren't government documents.
Unfortunately for the White House, this tactic will protect them from the curious citizen or watchdog group, but not a Congressional investigation. The White House can't claim executive privilege, since these are political communications.
At this point, those in the administration realize they are off the script - so they improvise-
(From the AP via TalkingPointsMemo)
The White House said Wednesday it had mishandled Republican Party-sponsored e-mail accounts used by nearly two dozen presidential aides, resulting in the loss of an undetermined number of e-mails concerning official White House business.Okay, so they're not being tiresome anymore - but just how freaking stupid do these people expect us be anyway?
Congressional investigators looking into the administration's firing of eight federal prosecutors already had the nongovernmental e-mail accounts in their sights because some White House aides used them to help plan the U.S. attorneys' ouster. Democrats were questioning whether the use of the GOP-provided e-mail accounts was proof that the firings were political.
I'm hoping a group of forensic computer specialists tear these idiots a new one.
The other shoe falls
JR was canned today.
Which turned today into a mad scramble to figure out:
1) What should have already been done
2) What has actually been done; and
3) What is on the near horizon
I was ramping up the person who will take up JR's slack when they stopped me up short.
"Before we get started, um... what happened?"
I'd completely forgotten about this aspect. Believing for so long that JR was on the way out for so long, I'd assumed that this was common knowledge to everyone. Given that most of us operate in relative isolation - people were understandably a bit mystified.
---
JR was likable - casual conversation, they'd be pretty entertaining up to a point. From the outside, people would see a person who is rushing on this or that project and think, "JR's got it together."
Except they didn't. At least, not in any way that was measurable.
They'd be able to talk around an issue, but any time you wanted hard answers - they just weren't there. JR was good at maintaining the facade. I don't know if they were intentionally deceptive - or if they really believed that they were busy and getting things done.
We all have moments when we're coasting at work: after you finish a big chunk of work, you're too sick/tired/inebriated to function at full throttle - it happens.
JR was like that every day. "I'm busy, I'm busy," but when you'd look over at them, they're shopping online, or on their cell, or surfing through a catalog - wasting time.
Worse, they just did the bare minimum on any project - then would puff it up like "wow, that was hard." With my boss out of town for over a week, I made it my business to make sure JR wasn't shipping the clients crap.
The more I looked, the worse it got. I tried to handle it internally - meet with JR - tell them the score - all I got was smiles and assurances, and the most polite form of pushback. They liked my "suggestions," but first they wanted to "get the boss's input as well."
i.e. Soon as you're not available, I'm going to feed the boss a line of crap. Then it'll be "I'd like to do what you say, but the boss said..."
Screw that.
---
Where was I? Anyway, CorpWorld can make you nervous and any time someone's plug gets pulled - everyone starts to wonder if they're on the bubble. JR's successor was expressing the very real fear that something they'd do in future would get them in trouble as well.
So I spill my guts on the subject. This seems to make them feel better - but it has the opposite effect for me.
This would be three times I've been in this boat, and each time the pattern repeats: people sidle up to me and ask (on the down-low, you understand) 'what the hell happened?'
It underscores the paranoia of CorpWorld, since these are people who, I would have thought, are completely secure in their professional life. Some of them have Masters degrees, some have Doctorates - these are people who should not worry. I'm some guy off the street with some working experience and a big mouth - I get to tell them not to worry?
Messed up.
Which turned today into a mad scramble to figure out:
1) What should have already been done
2) What has actually been done; and
3) What is on the near horizon
I was ramping up the person who will take up JR's slack when they stopped me up short.
"Before we get started, um... what happened?"
I'd completely forgotten about this aspect. Believing for so long that JR was on the way out for so long, I'd assumed that this was common knowledge to everyone. Given that most of us operate in relative isolation - people were understandably a bit mystified.
---
JR was likable - casual conversation, they'd be pretty entertaining up to a point. From the outside, people would see a person who is rushing on this or that project and think, "JR's got it together."
Except they didn't. At least, not in any way that was measurable.
They'd be able to talk around an issue, but any time you wanted hard answers - they just weren't there. JR was good at maintaining the facade. I don't know if they were intentionally deceptive - or if they really believed that they were busy and getting things done.
We all have moments when we're coasting at work: after you finish a big chunk of work, you're too sick/tired/inebriated to function at full throttle - it happens.
JR was like that every day. "I'm busy, I'm busy," but when you'd look over at them, they're shopping online, or on their cell, or surfing through a catalog - wasting time.
Worse, they just did the bare minimum on any project - then would puff it up like "wow, that was hard." With my boss out of town for over a week, I made it my business to make sure JR wasn't shipping the clients crap.
The more I looked, the worse it got. I tried to handle it internally - meet with JR - tell them the score - all I got was smiles and assurances, and the most polite form of pushback. They liked my "suggestions," but first they wanted to "get the boss's input as well."
i.e. Soon as you're not available, I'm going to feed the boss a line of crap. Then it'll be "I'd like to do what you say, but the boss said..."
Screw that.
---
Where was I? Anyway, CorpWorld can make you nervous and any time someone's plug gets pulled - everyone starts to wonder if they're on the bubble. JR's successor was expressing the very real fear that something they'd do in future would get them in trouble as well.
So I spill my guts on the subject. This seems to make them feel better - but it has the opposite effect for me.
This would be three times I've been in this boat, and each time the pattern repeats: people sidle up to me and ask (on the down-low, you understand) 'what the hell happened?'
It underscores the paranoia of CorpWorld, since these are people who, I would have thought, are completely secure in their professional life. Some of them have Masters degrees, some have Doctorates - these are people who should not worry. I'm some guy off the street with some working experience and a big mouth - I get to tell them not to worry?
Messed up.
Monday, April 09, 2007
"...we've traced the call, they're inside the building! Run!"
Working in a business as large as my current employer, I suppose I should not be surprised when I run into people I used to know. I live in the area, they (likely) live in the area - the odds aren't that long.
Previously, I'd run into a former co-worker from my past life (who I did not get on terribly well with) and managed to deal. They've moved on, I'd moved on - actually, there really wasn't anything to move on from. Start from zero.
For the past few weeks, I've been seeing (or swore I was seeing) somebody I used to know. Walking down the stairs, crossing the hall - Hey! was that...?
This was a person I'd always regarded as odd - they hung out in our group, mainly in the company of another associate who I've since lost track of.
This person was always.... odd. They'd eat food off of someone else's plate without asking - they'd make dark observations about topics of light conversation-
They were the sort of person you'd envision hearing someone describing in a newscast as "Quiet, always kept to themselves. Never would have suspected that they had a severed head in the fridge..."
That kind of person.
This person was known as potatohead, and now I see them everywhere.
Question is, now what do I do? I don't even remember their real name. One of these days, we'll end up in the elevator together and they'll say "hi," and I won't have the foggiest idea of what to say.
"Hey, how's the... uh? Remember when you creeped us all out that one time? Wow, that was... uh..."
Too freakin' weird.
Previously, I'd run into a former co-worker from my past life (who I did not get on terribly well with) and managed to deal. They've moved on, I'd moved on - actually, there really wasn't anything to move on from. Start from zero.
For the past few weeks, I've been seeing (or swore I was seeing) somebody I used to know. Walking down the stairs, crossing the hall - Hey! was that...?
This was a person I'd always regarded as odd - they hung out in our group, mainly in the company of another associate who I've since lost track of.
This person was always.... odd. They'd eat food off of someone else's plate without asking - they'd make dark observations about topics of light conversation-
They were the sort of person you'd envision hearing someone describing in a newscast as "Quiet, always kept to themselves. Never would have suspected that they had a severed head in the fridge..."
That kind of person.
This person was known as potatohead, and now I see them everywhere.
Question is, now what do I do? I don't even remember their real name. One of these days, we'll end up in the elevator together and they'll say "hi," and I won't have the foggiest idea of what to say.
"Hey, how's the... uh? Remember when you creeped us all out that one time? Wow, that was... uh..."
Too freakin' weird.
Monday, March 26, 2007
2008!? You gotta be sh!tting me!
If you don't watch the show - you'll have no idea what I'm talking about. But for those who do, and just did-
I feel the same way...!
ARRRRGH!
I feel the same way...!
ARRRRGH!
Friday, March 23, 2007
Single point of failure
A chopper pilot once told me that Hueys in Vietnam had a part that was euphemistically called the “Jesus bolt.” Its function was to hold the rotors onto the main mast, which led to its nickname. If that bolt failed, only Jesus could save you.
My backyard has a Jesus bolt. I used to think it was a 1/3 horsepower submersible sump pump. Today, I found out otherwise.
I’ll explain.
My backyard is the low spot in the neighborhood – which means that, sooner or later, I get everyone’s rainwater.
The previous owner of my house installed the aforementioned sump in the yard’s low spot.
Let me back up – ‘installed’ is a pretty strong word. What they actually did is dig a pit for the pump, run five feet of PVC below ground until they reached their neighbor’s yard.
So far, so good.
Next, they ran twenty feet of PVC above ground, on their neighbor’s side of the fence.
With me?
Then, they attached flex hose and buried it along the back of their neighbor’s property until it came out at the corner of four lots that didn’t belong to them.
It gets better.
They then plugged said pump into a 100’ industrial strength extension cord, and buried it in the backyard.
How did it get power?
You’d think given their earlier decisions, they’d just plug it into an outside receptacle, but no, they ran it through a basement window (which could no longer be sealed against the weather) and plugged it into a wall outlet.
Nice.
All this I know now. Learning all this happened in stages – the last stage happening yesterday.
In the beginning – I knew only that there was a buried extension cord, and that the water went…somewhere.
Like most people not looking for trouble, we let this sleeping beast lie until it bit us. One particularly rainy day I noticed that not only was my backyard underwater, but there was a patch of water churning violently in the back corner of my yard.
Being me, I slogged over to the spot and found the aforementioned above-ground-on-the-neighbor’s property PVC pipe. It had split down the side and the sump was dutifully pumping water out of the middle of my backyard lake, only to deposit it into said lake about fifteen feet away.
This, I did not like.
So I bought some PVC, tore out all the splintered junk (that presumably had been shattered by repeated encounters with my neighbor’s lawnmower) and put a fresh batch of PVC on my side of the fence and tied it into the flex hose. Still didn’t know where that hose went to, but I didn’t want to mess with success. I found that the hose went deep into the ground, but once the water was going away – my curiosity followed.
Enter dad.
Dad was not the type to leave such a half-assed monstrosity in place. First chance he got, he dragged me out in the back yard to mount an electrical outlet right next to the pump. We buried conduit and gave the outlet some protection from the elements.
Then we dug a trench and buried the PVC and tied it into the flex hose. In the process, we discovered that it let out on the other side of my neighbor’s yard.
Early discussions with my neighbors indicated that this was not an issue.
Problem solved, right? Wrong.
Why? Because my backyard has a Jesus bolt.
A few days ago, my backyard turned into a lake again and I slogged through the water to trip a stuck float arm. Hours later, the water was gone.
Yesterday, the yard is a lake again. Waiting the usual span of hours, I see no movement. I slog through the marsh and pull up the pump, expecting to free a stuck float arm.
Only this time, the pump is well and truly broken. Apparently, the float fail last time occurred when the float was pressed up against the side of the pump. The pump got so hot that it melted a hole in the float. The hole let in water to the point where the float couldn’t live up to its name.
Last time, hauling up the pump probably cleared out the water and allowed trapped air to float the arm and trigger the pump.
This time, however the pump had kept running so long that it apparently cooked itself – leaving me with something about as useful as a soggy, twelve pound paperweight.
Off to the hardware store – and I buy the same make and model. Lather, rinse, repeat.
Hook it up, plug it in. Presto! Water level falling.
Later that night – I’m on the back porch watching my neighbors dig out their sump and 50’ flex hose. They’re headed for my yard.
That’s odd. So I chat them up and they’re intending to drain my backyard lake. This is nice, I tell them, but my pump is working now and this should all go away soon.
And then they kill off any hope of an easy solution to this mess.
See, the back of their yard is flooding, too. Not where it’s adjacent to my yard, but on the other side – where my sump’s flex hose ends. I turn off the breaker to the sump and, yep, the water in their backyard starts to recede.
My sump is flooding their yard. This has never happened before – but it’s for damn sure I can’t ask them to endure flooding on account of my lack of follow through.
They’re nice about it, even offer to let me use their flex hose, but I’m pissed. Here I fix the faulty pump, and it turns out I've spent all this time patching a system that is totally doomed. I’m stuck with either running PVC out to the street, or shelling out the three grand it would take to re-grade the backyard.
Right now, I’m praying for a dry spring.
My backyard has a Jesus bolt. I used to think it was a 1/3 horsepower submersible sump pump. Today, I found out otherwise.
I’ll explain.
My backyard is the low spot in the neighborhood – which means that, sooner or later, I get everyone’s rainwater.
The previous owner of my house installed the aforementioned sump in the yard’s low spot.
Let me back up – ‘installed’ is a pretty strong word. What they actually did is dig a pit for the pump, run five feet of PVC below ground until they reached their neighbor’s yard.
So far, so good.
Next, they ran twenty feet of PVC above ground, on their neighbor’s side of the fence.
With me?
Then, they attached flex hose and buried it along the back of their neighbor’s property until it came out at the corner of four lots that didn’t belong to them.
It gets better.
They then plugged said pump into a 100’ industrial strength extension cord, and buried it in the backyard.
How did it get power?
You’d think given their earlier decisions, they’d just plug it into an outside receptacle, but no, they ran it through a basement window (which could no longer be sealed against the weather) and plugged it into a wall outlet.
Nice.
All this I know now. Learning all this happened in stages – the last stage happening yesterday.
In the beginning – I knew only that there was a buried extension cord, and that the water went…somewhere.
Like most people not looking for trouble, we let this sleeping beast lie until it bit us. One particularly rainy day I noticed that not only was my backyard underwater, but there was a patch of water churning violently in the back corner of my yard.
Being me, I slogged over to the spot and found the aforementioned above-ground-on-the-neighbor’s property PVC pipe. It had split down the side and the sump was dutifully pumping water out of the middle of my backyard lake, only to deposit it into said lake about fifteen feet away.
This, I did not like.
So I bought some PVC, tore out all the splintered junk (that presumably had been shattered by repeated encounters with my neighbor’s lawnmower) and put a fresh batch of PVC on my side of the fence and tied it into the flex hose. Still didn’t know where that hose went to, but I didn’t want to mess with success. I found that the hose went deep into the ground, but once the water was going away – my curiosity followed.
Enter dad.
Dad was not the type to leave such a half-assed monstrosity in place. First chance he got, he dragged me out in the back yard to mount an electrical outlet right next to the pump. We buried conduit and gave the outlet some protection from the elements.
Then we dug a trench and buried the PVC and tied it into the flex hose. In the process, we discovered that it let out on the other side of my neighbor’s yard.
Early discussions with my neighbors indicated that this was not an issue.
Problem solved, right? Wrong.
Why? Because my backyard has a Jesus bolt.
A few days ago, my backyard turned into a lake again and I slogged through the water to trip a stuck float arm. Hours later, the water was gone.
Yesterday, the yard is a lake again. Waiting the usual span of hours, I see no movement. I slog through the marsh and pull up the pump, expecting to free a stuck float arm.
Only this time, the pump is well and truly broken. Apparently, the float fail last time occurred when the float was pressed up against the side of the pump. The pump got so hot that it melted a hole in the float. The hole let in water to the point where the float couldn’t live up to its name.
Last time, hauling up the pump probably cleared out the water and allowed trapped air to float the arm and trigger the pump.
This time, however the pump had kept running so long that it apparently cooked itself – leaving me with something about as useful as a soggy, twelve pound paperweight.
Off to the hardware store – and I buy the same make and model. Lather, rinse, repeat.
Hook it up, plug it in. Presto! Water level falling.
Later that night – I’m on the back porch watching my neighbors dig out their sump and 50’ flex hose. They’re headed for my yard.
That’s odd. So I chat them up and they’re intending to drain my backyard lake. This is nice, I tell them, but my pump is working now and this should all go away soon.
And then they kill off any hope of an easy solution to this mess.
See, the back of their yard is flooding, too. Not where it’s adjacent to my yard, but on the other side – where my sump’s flex hose ends. I turn off the breaker to the sump and, yep, the water in their backyard starts to recede.
My sump is flooding their yard. This has never happened before – but it’s for damn sure I can’t ask them to endure flooding on account of my lack of follow through.
They’re nice about it, even offer to let me use their flex hose, but I’m pissed. Here I fix the faulty pump, and it turns out I've spent all this time patching a system that is totally doomed. I’m stuck with either running PVC out to the street, or shelling out the three grand it would take to re-grade the backyard.
Right now, I’m praying for a dry spring.
"...or else the terrorists win"
If you haven't read the anonymous article in the Washington Post regarding National Security Letters and what their effect is on law abiding citizens is, you really should.
from My National Security Letter Gag Order (login required):
To paraphrase Hans Gruber, "[the liberty and freedom the terrorists cannot destroy] is [destroyed] automatically in response to a terrorist incident. You ask for miracles, Theo? I give you the F. B. I."
from My National Security Letter Gag Order (login required):
Three years ago, I received a national security letter (NSL) in my capacity as the president of a small Internet access and consulting business. The letter ordered me to provide sensitive information about one of my clients. There was no indication that a judge had reviewed or approved the letter, and it turned out that none had. The letter came with a gag provision that prohibited me from telling anyone, including my client, that the FBI was seeking this information.
Living under the gag order has been stressful and surreal. Under the threat of criminal prosecution, I must hide all aspects of my involvement in the case -- including the mere fact that I received an NSL -- from my colleagues, my family and my friends. When I meet with my attorneys I cannot tell my girlfriend where I am going or where I have been. I hide any papers related to the case in a place where she will not look. When clients and friends ask me whether I am the one challenging the constitutionality of the NSL statute, I have no choice but to look them in the eye and lie.
To paraphrase Hans Gruber, "[the liberty and freedom the terrorists cannot destroy] is [destroyed] automatically in response to a terrorist incident. You ask for miracles, Theo? I give you the F. B. I."
Monday, March 19, 2007
Basketball diary
Blogging is a curious animal. Readers who don’t know you will miss context and subtext. Readers who do know you can make you self-conscious.
I’ve been trying the anonymous route to protect the narrative – but even so, there are things you just don’t bring up.
I’d been debating in my mind if the Basketball Weekend is one of them. For over a decade now, my friend G has been inviting people over to his place to watch the opening rounds of March Madness. On the surface, this is boilerplate enthusiasm for a chosen sport. We like basketball; ergo we watch basketball in a group. Saves electricity, we can pool resources for beer and chips.
It might have been that, early on, - but the reality of any situation changes over time. What began as an excuse to drink and swear and carry on about this team or that team, is pretty much evolved into the best opportunity I have to see my old friends and step out of parenthood for awhile.
As I’m only starting to appreciate - those are two huge things in life. These are guys who I’ve known since – hell, since Bush the Elder was president. Given my background - outside of family, these are the people I’ve known the longest. We don’t chat regularly, so this is pretty much the only opportunity to catch up with them.
I remember C (of A&C) telling me once that she’d interviewed a co-worker for a project and one of the questions she’d asked was pretty typical: what do you know now that you wished you’d learned earlier? That sort of thing. Her co-worker had given a response that was pretty memorable: “I wish I’d realized how important people were a lot sooner in life.”
That’s always resonated with me. Growing up, my social life got erased every couple of years when we’d move – and I think I got more than I little used to writing people off when they were out of sight. I believe that this led to an alarming amount of selfish behavior on my part. I still do things that are (in retrospect) amazingly self-centered for a father of two. Of course, you appreciate the people around you – but investing in them is something I’ve been very bad at.
The Basketball Weekend has been G’s investment in his friends (I’m sure he doesn’t look at it this way) but boiled down – he makes his house available to everyone and we all benefit from hanging out together. March Madness is the excuse – but it’s just great to hang around with people who “knew you when.”
Reverting to selfish for a moment, it is worth pointing out that seeing your friends with their families is one thing – seeing them sans family is quite another. Stereotypically, this would mean the guys sit around acting lewd and chauvinistic because their wives aren’t around to carp on them – but this isn’t really what I’m talking about.
With my son and daughter around – I’m plugged into parenthood. Conversation steers away from subjects that aren’t fit for children and congeals around topics that address the current behavior of same. This is fine and good, but sitting in a roomful of adults, getting to talk like adults is one of the reasons there are bowling leagues and book clubs.
It is therapy. We can grouse about the things that cannot be fixed, discuss the world’s problems, or just forget everything and rally around the fact that Duke can’t seem to drain a basket whenever CBS coverage switches to Hi-Def (So long, Dukies – we won’t miss you).
It is not mere nostalgia, or escape – it’s an awful lot of things that I wasn’t sure I could (or should) spell out.
In the interests of splitting the difference, I’ll leave some things out.
I will not, for example – discuss drinking cocktails at ten in the morning.
I won’t go into details about when four of us watched two men wrestle in the nude.
-or how C made a waitress dance for him before kissing her (and him, a married man!) or any of that stuff.
Some things are just sacred.
I’ve been trying the anonymous route to protect the narrative – but even so, there are things you just don’t bring up.
I’d been debating in my mind if the Basketball Weekend is one of them. For over a decade now, my friend G has been inviting people over to his place to watch the opening rounds of March Madness. On the surface, this is boilerplate enthusiasm for a chosen sport. We like basketball; ergo we watch basketball in a group. Saves electricity, we can pool resources for beer and chips.
It might have been that, early on, - but the reality of any situation changes over time. What began as an excuse to drink and swear and carry on about this team or that team, is pretty much evolved into the best opportunity I have to see my old friends and step out of parenthood for awhile.
As I’m only starting to appreciate - those are two huge things in life. These are guys who I’ve known since – hell, since Bush the Elder was president. Given my background - outside of family, these are the people I’ve known the longest. We don’t chat regularly, so this is pretty much the only opportunity to catch up with them.
I remember C (of A&C) telling me once that she’d interviewed a co-worker for a project and one of the questions she’d asked was pretty typical: what do you know now that you wished you’d learned earlier? That sort of thing. Her co-worker had given a response that was pretty memorable: “I wish I’d realized how important people were a lot sooner in life.”
That’s always resonated with me. Growing up, my social life got erased every couple of years when we’d move – and I think I got more than I little used to writing people off when they were out of sight. I believe that this led to an alarming amount of selfish behavior on my part. I still do things that are (in retrospect) amazingly self-centered for a father of two. Of course, you appreciate the people around you – but investing in them is something I’ve been very bad at.
The Basketball Weekend has been G’s investment in his friends (I’m sure he doesn’t look at it this way) but boiled down – he makes his house available to everyone and we all benefit from hanging out together. March Madness is the excuse – but it’s just great to hang around with people who “knew you when.”
Reverting to selfish for a moment, it is worth pointing out that seeing your friends with their families is one thing – seeing them sans family is quite another. Stereotypically, this would mean the guys sit around acting lewd and chauvinistic because their wives aren’t around to carp on them – but this isn’t really what I’m talking about.
With my son and daughter around – I’m plugged into parenthood. Conversation steers away from subjects that aren’t fit for children and congeals around topics that address the current behavior of same. This is fine and good, but sitting in a roomful of adults, getting to talk like adults is one of the reasons there are bowling leagues and book clubs.
It is therapy. We can grouse about the things that cannot be fixed, discuss the world’s problems, or just forget everything and rally around the fact that Duke can’t seem to drain a basket whenever CBS coverage switches to Hi-Def (So long, Dukies – we won’t miss you).
It is not mere nostalgia, or escape – it’s an awful lot of things that I wasn’t sure I could (or should) spell out.
In the interests of splitting the difference, I’ll leave some things out.
I will not, for example – discuss drinking cocktails at ten in the morning.
I won’t go into details about when four of us watched two men wrestle in the nude.
-or how C made a waitress dance for him before kissing her (and him, a married man!) or any of that stuff.
Some things are just sacred.
Wednesday, March 07, 2007
Incommunicado
Mom's been the vector of family news for some time now - I hear about it because everybody calls her. Nobody call me because - quite frankly - I never call them.
This past week, mom was traveling in the Grand Canyon. No cell, no internet. So mom's off taking nature photos and somewhere, her phone was ringing off the hook.
Two long-delayed items finally happened, and neither of them were good.
First up - My uncle K had to put his dog Scooby to sleep. Scooby was the smartest, mildest, most user-friendly dog I ever knew. He was like my uncle - very low key, did his own thing - just a great hound dog all round. No great mystery or surprise, Scoob was getting old - and nature took its course. Just a shame.
The closer was also no surprise, just a sad end to a sadder story.
DB, Dad's cousin, lost his wife, JB last week. She had been suffering for years with that particularly cruel form of alzheimers that allows you to be fully functional, yet forget even basic things like speaking. I'd last spoken to DB at dad's funeral, and he was there alone. I knew it was bad, and we avoided the subject. I last saw her at the local festival and she'd smiled a lot and said nothing. After we'd said our goodbyes, Dad had pointed out that she wasn't shy - she just forgot how to talk somedays. She would have been about my dad's age - way too young for a disease like that. DB was like my grandfather, taking care of a person who didn't even know who he was. I can't even imagine.
So there's an end to their suffering, but it is such a dreadful thing. Alzheimers is called the "Long Goodbye," but it’s so much worse than that. By the time it finally consents to let you go, your loved ones are usually too spent to grieve in any normal way. DB's family has not had an easy go of it for lots of reasons - they just never get a break.
Dad would have been there - I would have gladly stood in for him.
I just wish I'd heard about it in time to do something.
This past week, mom was traveling in the Grand Canyon. No cell, no internet. So mom's off taking nature photos and somewhere, her phone was ringing off the hook.
Two long-delayed items finally happened, and neither of them were good.
First up - My uncle K had to put his dog Scooby to sleep. Scooby was the smartest, mildest, most user-friendly dog I ever knew. He was like my uncle - very low key, did his own thing - just a great hound dog all round. No great mystery or surprise, Scoob was getting old - and nature took its course. Just a shame.
The closer was also no surprise, just a sad end to a sadder story.
DB, Dad's cousin, lost his wife, JB last week. She had been suffering for years with that particularly cruel form of alzheimers that allows you to be fully functional, yet forget even basic things like speaking. I'd last spoken to DB at dad's funeral, and he was there alone. I knew it was bad, and we avoided the subject. I last saw her at the local festival and she'd smiled a lot and said nothing. After we'd said our goodbyes, Dad had pointed out that she wasn't shy - she just forgot how to talk somedays. She would have been about my dad's age - way too young for a disease like that. DB was like my grandfather, taking care of a person who didn't even know who he was. I can't even imagine.
So there's an end to their suffering, but it is such a dreadful thing. Alzheimers is called the "Long Goodbye," but it’s so much worse than that. By the time it finally consents to let you go, your loved ones are usually too spent to grieve in any normal way. DB's family has not had an easy go of it for lots of reasons - they just never get a break.
Dad would have been there - I would have gladly stood in for him.
I just wish I'd heard about it in time to do something.
Friday, March 02, 2007
Wisdom of the day
Saw this on Google:
People often write me and ask how I keep my wood floors so clean when I live with a child and a dog, and my answer is that I use a technique called Suffering From a Mental Illness. - Heather Armstrong
Thursday, March 01, 2007
The writing on the wall
CorpWorld is an odd place. Most times - people are unfailingly polite. I believe that CorpWorld culture mandates this, a sort of enforced cheeriness I've taken to calling "North Korea Nice."
Your tech contact will politely smile and nod while you say your peace - then tell their manager that you are causing problems on the project. This will become obvious to you when your manager shows up out of the blue to discuss topics that could only have been suggested by the aforementioned tech contact.
In theory at least, conflicts are resolved by proxy - and no one loses face. Of course, the reality is that plenty of face is lost, and any lag in the system means that people will keep doing whatever got them in trouble until they eventually find out. This fact is compounded when those making the complaint know you're in trouble before you do.
This can make for some interesting meetings, as you sit with a roomful of people all wearing smug expressions on their faces.
Which brings us to a person called JR. JR is going to be fired.
This is fact in the same sense that a person who steps in front of a Mack truck is dead. A miracle could happen, Superman could do the fly-round-the-world thing he does, but odds are - they're pretty much toast.
So it is with JR, but they don't know it yet.
JR's been slacking and it's starting to show. I've seen their face time in front of clients get pruned back again and again, and they are being asked to do more grunt-tasks and less brain-tasks. Rather than seeing this for what it is, they have chosen to feel persecuted.
Worse, they are committing the one truly unpardonable sin in CorpWorld - they are making their department look unprofessional. Our department’s higher ups will tolerate an awful lot. However, if they have to choose between an employee and their own credibility, they'll pause a moment - if they like you - and then fire your ass.
Being in meetings with JR has become a little surreal. Ostensibly, nothing has changed and they are still responsible for running some internal meetings. But it's obvious to all that JR is in trouble. I may be the only one who thinks that JR's condition is terminal - but I've seen this same pattern twice now, and all the signs are there.
Having drunk the Kool-Aid, nobody tells JR a thing - we just smile and carry on. The moral paragons of the world would offer a warning - surely a warning isn't out of line - but I'm not stepping up any time soon. I'm right, but I can't prove it - and anything I'll say won't change a damn thing.
I can't say I have much sympathy for JR - management has been (from what I can tell) fair. But the fact that this situation has carried on so long essentially makes co-conspirators out of everyone who works with JR. We discuss the issue when they aren't around, and hush up when they show up. Nobody has hard info from a reliable source, but we're not stupid.
JR's going to "see their account rep" sometime in the next month or so - and we'll all just keep smiling until it happens.
Just another day in corporate land.
Your tech contact will politely smile and nod while you say your peace - then tell their manager that you are causing problems on the project. This will become obvious to you when your manager shows up out of the blue to discuss topics that could only have been suggested by the aforementioned tech contact.
In theory at least, conflicts are resolved by proxy - and no one loses face. Of course, the reality is that plenty of face is lost, and any lag in the system means that people will keep doing whatever got them in trouble until they eventually find out. This fact is compounded when those making the complaint know you're in trouble before you do.
This can make for some interesting meetings, as you sit with a roomful of people all wearing smug expressions on their faces.
Which brings us to a person called JR. JR is going to be fired.
This is fact in the same sense that a person who steps in front of a Mack truck is dead. A miracle could happen, Superman could do the fly-round-the-world thing he does, but odds are - they're pretty much toast.
So it is with JR, but they don't know it yet.
JR's been slacking and it's starting to show. I've seen their face time in front of clients get pruned back again and again, and they are being asked to do more grunt-tasks and less brain-tasks. Rather than seeing this for what it is, they have chosen to feel persecuted.
Worse, they are committing the one truly unpardonable sin in CorpWorld - they are making their department look unprofessional. Our department’s higher ups will tolerate an awful lot. However, if they have to choose between an employee and their own credibility, they'll pause a moment - if they like you - and then fire your ass.
Being in meetings with JR has become a little surreal. Ostensibly, nothing has changed and they are still responsible for running some internal meetings. But it's obvious to all that JR is in trouble. I may be the only one who thinks that JR's condition is terminal - but I've seen this same pattern twice now, and all the signs are there.
Having drunk the Kool-Aid, nobody tells JR a thing - we just smile and carry on. The moral paragons of the world would offer a warning - surely a warning isn't out of line - but I'm not stepping up any time soon. I'm right, but I can't prove it - and anything I'll say won't change a damn thing.
I can't say I have much sympathy for JR - management has been (from what I can tell) fair. But the fact that this situation has carried on so long essentially makes co-conspirators out of everyone who works with JR. We discuss the issue when they aren't around, and hush up when they show up. Nobody has hard info from a reliable source, but we're not stupid.
JR's going to "see their account rep" sometime in the next month or so - and we'll all just keep smiling until it happens.
Just another day in corporate land.
Saturday, February 24, 2007
Sweet Jesus, how I F-ing hate children's car seats
*ahem*
Just needed to be said.
Move along, now. Nothing to see here.
Just needed to be said.
Move along, now. Nothing to see here.
Tuesday, February 13, 2007
Fratricide
Test over. It’s time for the report. We have a protocol that you cannot test a design that you helped develop. This means that my test’s final report will be written up and presented by the people who conducted it.
They’re a good crew. The facilitator, SR, appears a bit casual - but they are a whiz at avoiding leading questions and practicing self-restraint. A person who knows the answer has to work hard not to hint to a participant who is struggling – SR is an ace at just responding minimally and getting the participant to explain their thought process.
SR is paired up with a serious usability pro, KR, so the report is sure to be airtight and professional. They are offsite, so we’ve scheduled a videoconference so the clients and developers can hear the report and ask questions.
Given the fact that my test plan has missed a key objective – I’m expecting to get tagged on the report. SR and KR won’t ding me for my plan – but a public reading of their findings can only highlight the gap in what I’d asked them to find out. I’m genuinely sweating it.
It’s the last item of the day, and all my other meetings cancel – so I’ve got all day to imagine the myriad ways SR will say “we don’t have much data on X.”
I ping SR twice about the report. “Make sure you hit the main test objectives first, the clients won’t want to hear about ancillary stuff until they have the big stuff.” I ask about a finding they mentioned in passing. I’m wondering if this finding will re-open old arguments with the Client. I get some assurances and go to lunch.
At work, I’ve been ever the optimist – but I just can’t relax. I hit one of the few decent restaurants near work and tell myself I might as well eat first.
Last time we used KR and SR, there were some communication errors that resulted in findings that were beyond the scope of the project, or made it look like my department didn’t understand the project they were working on. I’ve tried to minimize this risk as much as I can – but there’s so much information to get across. I’m afraid that SR will say something that will make us lose cred.
My department, we’re a latecomer to most projects, and we are generally regarded as just another mouth to feed. I’m convinced half the time that the Client would happily be rid of us – but somebody above them is forcing them to work with us.
The history of this project has been tumultuous – I smoke-jumped in just as people were getting canned. The timeline and scope keep getting changed in threatening ways – and we’ve been at loggerheads in design because the culture is “don’t change anything.” It’s the classic usability problem. Developers want the UI to look like the back-end code, the SME’s assume that everyone using the system eats and sleeps the operations manual, just like they do – it’s a mess.
I’ve gone out on a limb countless times, just to see if I can provoke discussions that lead us away from “do it the way we do now.” I’ve been shot down so many times, I’ve stopped noticing - but I’m determined to at least try to make things better.
Very rarely, one of our ideas gets approved, and my team celebrates. Sure, the whole design is a Frankenstein’s monster – but there’s this little part (call it function X) that we got into the project. We think it’s neat – we hope it lives until go-live.
It’s been a real struggle – and patience on some issues has worn so thin that we’ve abandoned all discussion of them. We’re just hoping that once things have cooled off, we can revisit them in better times.
So, here we are – having amassed a modest amount of cred – and I’m waiting for this presentation to highlight my test’s poor design.
I’ve told SR that he should plow through the biggies and expect interruptions. My group prefers the piranha method of discussion, so any suggestion that we hold questions is just a waste.
And we start.
---
SR starts on the part of the UI that I failed to evaluate against a previous design. Participants encountering the new design failed to see and interact with it 100% of the time.
No biggie, we just prompt them to look at it and observe their reactions to it with a prompt. Having seen most of the sessions – I know that most people were able to use the UI with a prompt. This is not ideal, but it means that our problem is likely one of visibility and labeling rather than actual function.
Except SR didn’t see it that way. SR details failure after failure in this UI even after prompts. This I do not recall, but I wasn’t at all the sessions. I’m a bit surprised, because this is a key piece of UI that two projects were waiting for. I’d thought (and unfortunately, said) that the issues with it were cosmetic and we could probably fix it easily. SR details a series of convincing issues that say otherwise. One of the project managers, short on time, expresses alarm and then leaves.
SR continues into another section I thought went well and proceeds to document why it is unadulterated crap. I’m really not liking where this is going.
Questions? The room is dead quiet. Everybody’s here, project managers, the Client, my boss – nobody says a thing.
It’s my show on this end, so I just tell SR to plow onward and they do. Right into a pet issue of mine. One of those little victories that I’d endured weeks of abuse to get into the design is now being held up as a cautionary tale. The Client and I were on opposite sides of this one and I’d carried the day mainly on persistence. Now, SR is basically listing all the same complaints the Client gave me when I first came up with the design.
The Client and the rest of the dev team go quiet – they remember the same discussions. They thought I was nuts – and SR is telling them all they were right to say so.
Now, normally, stuff like this – I don’t care. A design dies, but you make a better one out of the ashes. Everybody’s design takes a pounding, everyone gets a turn. But with this crowd, there will be people who will use this moment to discount any future input from me.
It’s dead quiet. SR’s clearly a bit surprised by this, and tries to liven things up. He addresses me directly “You look like you have something intelligent to say.”
I’m about to reply when I’m cut off –
“No, he doesn’t” says the Client, scoffing.
We have a few pro forma questions and then it’s time to go.
---
SR’s report was honest and accurate – yet it managed to hit every issue where the Client had doubts about us and strengthen them. I’m absolutely stunned.
My boss is gone. No chance to debrief. One of the more sympathetic types comes up and says “Back to the drawing board, eh?” I’m looking over at the Client, who is in a huddle with the people they still have respect for.
I can’t even get my head around this. Every discussion after this will be uphill times ten.
Next meeting, all my suggestions will be stillborn – the Client may want me off their project and my boss, too for all I know.
I don’t blame SR at all – these were honest conclusions, but what are the odds that all the stuff singled out for abuse would be mine? Yeah, I know law of averages, but did it have to frickin' happen now??!!
All this fighting for a place at the table, some respect and now –
Shit. Square one if I’m lucky.
They’re a good crew. The facilitator, SR, appears a bit casual - but they are a whiz at avoiding leading questions and practicing self-restraint. A person who knows the answer has to work hard not to hint to a participant who is struggling – SR is an ace at just responding minimally and getting the participant to explain their thought process.
SR is paired up with a serious usability pro, KR, so the report is sure to be airtight and professional. They are offsite, so we’ve scheduled a videoconference so the clients and developers can hear the report and ask questions.
Given the fact that my test plan has missed a key objective – I’m expecting to get tagged on the report. SR and KR won’t ding me for my plan – but a public reading of their findings can only highlight the gap in what I’d asked them to find out. I’m genuinely sweating it.
It’s the last item of the day, and all my other meetings cancel – so I’ve got all day to imagine the myriad ways SR will say “we don’t have much data on X.”
I ping SR twice about the report. “Make sure you hit the main test objectives first, the clients won’t want to hear about ancillary stuff until they have the big stuff.” I ask about a finding they mentioned in passing. I’m wondering if this finding will re-open old arguments with the Client. I get some assurances and go to lunch.
At work, I’ve been ever the optimist – but I just can’t relax. I hit one of the few decent restaurants near work and tell myself I might as well eat first.
Last time we used KR and SR, there were some communication errors that resulted in findings that were beyond the scope of the project, or made it look like my department didn’t understand the project they were working on. I’ve tried to minimize this risk as much as I can – but there’s so much information to get across. I’m afraid that SR will say something that will make us lose cred.
My department, we’re a latecomer to most projects, and we are generally regarded as just another mouth to feed. I’m convinced half the time that the Client would happily be rid of us – but somebody above them is forcing them to work with us.
The history of this project has been tumultuous – I smoke-jumped in just as people were getting canned. The timeline and scope keep getting changed in threatening ways – and we’ve been at loggerheads in design because the culture is “don’t change anything.” It’s the classic usability problem. Developers want the UI to look like the back-end code, the SME’s assume that everyone using the system eats and sleeps the operations manual, just like they do – it’s a mess.
I’ve gone out on a limb countless times, just to see if I can provoke discussions that lead us away from “do it the way we do now.” I’ve been shot down so many times, I’ve stopped noticing - but I’m determined to at least try to make things better.
Very rarely, one of our ideas gets approved, and my team celebrates. Sure, the whole design is a Frankenstein’s monster – but there’s this little part (call it function X) that we got into the project. We think it’s neat – we hope it lives until go-live.
It’s been a real struggle – and patience on some issues has worn so thin that we’ve abandoned all discussion of them. We’re just hoping that once things have cooled off, we can revisit them in better times.
So, here we are – having amassed a modest amount of cred – and I’m waiting for this presentation to highlight my test’s poor design.
I’ve told SR that he should plow through the biggies and expect interruptions. My group prefers the piranha method of discussion, so any suggestion that we hold questions is just a waste.
And we start.
---
SR starts on the part of the UI that I failed to evaluate against a previous design. Participants encountering the new design failed to see and interact with it 100% of the time.
No biggie, we just prompt them to look at it and observe their reactions to it with a prompt. Having seen most of the sessions – I know that most people were able to use the UI with a prompt. This is not ideal, but it means that our problem is likely one of visibility and labeling rather than actual function.
Except SR didn’t see it that way. SR details failure after failure in this UI even after prompts. This I do not recall, but I wasn’t at all the sessions. I’m a bit surprised, because this is a key piece of UI that two projects were waiting for. I’d thought (and unfortunately, said) that the issues with it were cosmetic and we could probably fix it easily. SR details a series of convincing issues that say otherwise. One of the project managers, short on time, expresses alarm and then leaves.
SR continues into another section I thought went well and proceeds to document why it is unadulterated crap. I’m really not liking where this is going.
Questions? The room is dead quiet. Everybody’s here, project managers, the Client, my boss – nobody says a thing.
It’s my show on this end, so I just tell SR to plow onward and they do. Right into a pet issue of mine. One of those little victories that I’d endured weeks of abuse to get into the design is now being held up as a cautionary tale. The Client and I were on opposite sides of this one and I’d carried the day mainly on persistence. Now, SR is basically listing all the same complaints the Client gave me when I first came up with the design.
The Client and the rest of the dev team go quiet – they remember the same discussions. They thought I was nuts – and SR is telling them all they were right to say so.
Now, normally, stuff like this – I don’t care. A design dies, but you make a better one out of the ashes. Everybody’s design takes a pounding, everyone gets a turn. But with this crowd, there will be people who will use this moment to discount any future input from me.
Remember that one thing? How you insisted it was better? Well, you were wrong, so shaddup!SR’s report plows onward, ripping on two other items that I’ll take the fall for, before finally winding down on issues that were too minor for the team to care much about.
It’s dead quiet. SR’s clearly a bit surprised by this, and tries to liven things up. He addresses me directly “You look like you have something intelligent to say.”
I’m about to reply when I’m cut off –
“No, he doesn’t” says the Client, scoffing.
We have a few pro forma questions and then it’s time to go.
---
SR’s report was honest and accurate – yet it managed to hit every issue where the Client had doubts about us and strengthen them. I’m absolutely stunned.
My boss is gone. No chance to debrief. One of the more sympathetic types comes up and says “Back to the drawing board, eh?” I’m looking over at the Client, who is in a huddle with the people they still have respect for.
I can’t even get my head around this. Every discussion after this will be uphill times ten.
Next meeting, all my suggestions will be stillborn – the Client may want me off their project and my boss, too for all I know.
I don’t blame SR at all – these were honest conclusions, but what are the odds that all the stuff singled out for abuse would be mine? Yeah, I know law of averages, but did it have to frickin' happen now??!!
All this fighting for a place at the table, some respect and now –
Shit. Square one if I’m lucky.
Thursday, February 08, 2007
Rockstar
Like most jobs, mine has its share of drudgery. But one thing I do (that I have to do) I truly enjoy.
I get to test software on people.
Yeah, I know - that doesn't sound like much, but in my line of work - it’s the Superbowl. Testing a design with typical users and seeing how the software can be made better.
There is considerable debate as to whether or not this is science, art, or outright chicanery - but I think anyone who has participated in a lab test would agree - it gets your attention.
Having spent months in design, hashing out what an application needs to do - then spending more months designing a good way to do it - you finally put a prototype in front of someone and see what they think of it.
I may be mentally ill, but to me, it's a hell of a good time.
The doomsday project has stabilized to the point that it almost doesn't deserve the name, and I've spent the past month or so putting together testing scenarios and trying to find the best way to get a user to interact with the interface in ways that will give us useful feedback.
This is not easy. The first rule of user testing is that the participants will always surprise you. A task you are sure will be simple will prove maddeningly difficult for them. Participants will fly through your thorniest scenario with ease, only to fail on task because you made a bad choice in labeling the final "commit" button.
The ideal is to give users tasks that they would perform in real life. Then, maybe they'll act like it's real - and then maybe they'll even tell you what they really think. My scenarios are (to my mind) real-world, hands-off - but touch on all the design elements we care about. Trying to find the right mix of organic observation and manipulation can drive you nuts.
That said, testing week is like a carnival. AV setups - recording software - network connections, scheduling people, blah blah blah. I have to run a meeting tomorrow, I owe project work for other things - everything gets benched. People want the test results, they'll just have to deal.
Our prototype is (at least to my mind) a miracle of JavaScript posing as a live system. We have a design that would probably be easier to code as a working system than to simulate with script - but it's ready.
I start cataloging a list of all the things that could go wrong.
One by one, they don't.
The participants show up - despite subzero temperatures and crappy roads.
Inevitable shortcomings of a prototype do not break our test.
People tell us what they think.
The videoconference works.
IMing remote questions proves useful.
Our new screen capture software not only works, but is pretty damn cool.
Me and my team are loving it. We toast our prototyper.
Rockstar!
This becomes our chosen word of congratulations.
When the facilitator deftly handles a test snag, or when the notetaker pulls off the always-elusive "How do I ask this without telling them the answer?" question, over and over.
Rockstar!
We're getting really great comments - people are tanking on one task, but we know why - so we can fix it. All sorts of side comments are pointing out the vast difference between how our users actually work - and how our developers think they do. I'm drafting a list of follow up issues for other projects that are just starting up - so we can head off some really bad choices.
Living the life.
My boss comes in. They love the prototype, shower the team with praise. Rockstar!
The Client walks in. Wow.
This is a good thing. Most times, we can't get dev types or clients in the room to see what we see. The mere possibility that a client could actually watch a participant is great for us.
Assumptions are made in corp-world that have no basis in reality. Seeing a participant struggle with someone's pet design will usually trump business politics and get needed improvements a shot in the arm.
Participants aren't shy. They loudly announce that the corporate types have no idea what their needs are, point out workflow shortcomings and highlight obvious improvements that have somehow remained undone for years.
Our team has fought tooth and nail for credibility on this project. Lord knows, the H situation cost us heavily. We can really gain some corp-cred - if nothing goes wrong for this session.
I know what you're thinking, but nothing does go wrong. Aside from being overly talkative, the session goes much like previous sessions. Problems on the known issue, A/B testing results about the same. A few choice comments about the interface, and fade to black.
Me and my team are smug - cracking wise and cutting up on the IM.
I'm jazzed. I turn to the Client. "I can see some obvious improvements to this area of the design, but once people understand what it is trying to do - they do it easily."
The Client is un-moved. "This new design is replacing a prior one. There is nothing in this test that will allow me to compare the new design to the old. I still don't know which design is more successful."
I start with my list of proposed improvements to the new design. Our prototyper starts to chime in.
Client addresses the prototyper like I'm not even there. "We started with two options, we still have them - and we get nothing definitive about them from this test. I saw that as soon as the test started."
All the air goes out of the room. Client's right. I've put together this whole thing and I've missed one of the main goals. Client could care less about my list of findings, our list of issues, much less our ideas for future projects.
Three weeks delay, two huge projects waiting for the results of this test - and here we are, right back at a guessing game because I didn't force my participants to make a choice.
Client spells out what they would have done to get this answer - and I'm just sitting there taking it.
About the time they're done, my laptop fires off a warning shot - my boss has invited me to a meeting about some other project on the other side of campus in about three minutes.
I'm ten minutes late if I hurry.
I grab my things and bail - I've lost all cred with the Client, and now they get to watch me scramble to get my things and dash off to a meeting I've forgotten.
The whole way there, I'm just projecting the fallout. "Hey, nice test! Looked like fun! Complete waste of time, though." I'm too spent to even start on damage control. The benched work is rushing up in my mind - that roomful of people in tomorrow's meeting (that I haven't prepped for), I'm envisioning a really fun Q & A session...
And just like that, it's doomsday again.
I get to test software on people.
Yeah, I know - that doesn't sound like much, but in my line of work - it’s the Superbowl. Testing a design with typical users and seeing how the software can be made better.
There is considerable debate as to whether or not this is science, art, or outright chicanery - but I think anyone who has participated in a lab test would agree - it gets your attention.
Having spent months in design, hashing out what an application needs to do - then spending more months designing a good way to do it - you finally put a prototype in front of someone and see what they think of it.
I may be mentally ill, but to me, it's a hell of a good time.
The doomsday project has stabilized to the point that it almost doesn't deserve the name, and I've spent the past month or so putting together testing scenarios and trying to find the best way to get a user to interact with the interface in ways that will give us useful feedback.
This is not easy. The first rule of user testing is that the participants will always surprise you. A task you are sure will be simple will prove maddeningly difficult for them. Participants will fly through your thorniest scenario with ease, only to fail on task because you made a bad choice in labeling the final "commit" button.
The ideal is to give users tasks that they would perform in real life. Then, maybe they'll act like it's real - and then maybe they'll even tell you what they really think. My scenarios are (to my mind) real-world, hands-off - but touch on all the design elements we care about. Trying to find the right mix of organic observation and manipulation can drive you nuts.
That said, testing week is like a carnival. AV setups - recording software - network connections, scheduling people, blah blah blah. I have to run a meeting tomorrow, I owe project work for other things - everything gets benched. People want the test results, they'll just have to deal.
Our prototype is (at least to my mind) a miracle of JavaScript posing as a live system. We have a design that would probably be easier to code as a working system than to simulate with script - but it's ready.
I start cataloging a list of all the things that could go wrong.
One by one, they don't.
The participants show up - despite subzero temperatures and crappy roads.
Inevitable shortcomings of a prototype do not break our test.
People tell us what they think.
The videoconference works.
IMing remote questions proves useful.
Our new screen capture software not only works, but is pretty damn cool.
Me and my team are loving it. We toast our prototyper.
Rockstar!
This becomes our chosen word of congratulations.
When the facilitator deftly handles a test snag, or when the notetaker pulls off the always-elusive "How do I ask this without telling them the answer?" question, over and over.
Rockstar!
We're getting really great comments - people are tanking on one task, but we know why - so we can fix it. All sorts of side comments are pointing out the vast difference between how our users actually work - and how our developers think they do. I'm drafting a list of follow up issues for other projects that are just starting up - so we can head off some really bad choices.
Living the life.
My boss comes in. They love the prototype, shower the team with praise. Rockstar!
The Client walks in. Wow.
This is a good thing. Most times, we can't get dev types or clients in the room to see what we see. The mere possibility that a client could actually watch a participant is great for us.
Assumptions are made in corp-world that have no basis in reality. Seeing a participant struggle with someone's pet design will usually trump business politics and get needed improvements a shot in the arm.
Participants aren't shy. They loudly announce that the corporate types have no idea what their needs are, point out workflow shortcomings and highlight obvious improvements that have somehow remained undone for years.
Our team has fought tooth and nail for credibility on this project. Lord knows, the H situation cost us heavily. We can really gain some corp-cred - if nothing goes wrong for this session.
I know what you're thinking, but nothing does go wrong. Aside from being overly talkative, the session goes much like previous sessions. Problems on the known issue, A/B testing results about the same. A few choice comments about the interface, and fade to black.
Me and my team are smug - cracking wise and cutting up on the IM.
I'm jazzed. I turn to the Client. "I can see some obvious improvements to this area of the design, but once people understand what it is trying to do - they do it easily."
The Client is un-moved. "This new design is replacing a prior one. There is nothing in this test that will allow me to compare the new design to the old. I still don't know which design is more successful."
I start with my list of proposed improvements to the new design. Our prototyper starts to chime in.
Client addresses the prototyper like I'm not even there. "We started with two options, we still have them - and we get nothing definitive about them from this test. I saw that as soon as the test started."
All the air goes out of the room. Client's right. I've put together this whole thing and I've missed one of the main goals. Client could care less about my list of findings, our list of issues, much less our ideas for future projects.
Three weeks delay, two huge projects waiting for the results of this test - and here we are, right back at a guessing game because I didn't force my participants to make a choice.
Client spells out what they would have done to get this answer - and I'm just sitting there taking it.
About the time they're done, my laptop fires off a warning shot - my boss has invited me to a meeting about some other project on the other side of campus in about three minutes.
I'm ten minutes late if I hurry.
I grab my things and bail - I've lost all cred with the Client, and now they get to watch me scramble to get my things and dash off to a meeting I've forgotten.
The whole way there, I'm just projecting the fallout. "Hey, nice test! Looked like fun! Complete waste of time, though." I'm too spent to even start on damage control. The benched work is rushing up in my mind - that roomful of people in tomorrow's meeting (that I haven't prepped for), I'm envisioning a really fun Q & A session...
And just like that, it's doomsday again.
Tuesday, January 30, 2007
Pulling the plug
Can Congress force the President to pull out of Iraq?
Well, they've done it before - and by "they" I mean the very people who claim it can't be done.
Not that I wouldn't put it past the Dems to have arguing the reverse of their current position, either - but it shows you how fickle the GOP can be when their policy is on the chopping block.
Glenn Greenwald has them by the short hairs.
Well, they've done it before - and by "they" I mean the very people who claim it can't be done.
Not that I wouldn't put it past the Dems to have arguing the reverse of their current position, either - but it shows you how fickle the GOP can be when their policy is on the chopping block.
Glenn Greenwald has them by the short hairs.
Tuesday, January 23, 2007
Stand up if you hate Man U
A few years back, in the game they call football, my chosen team had a nemesis. My team were likable underachievers. Their rivals were the media darlings - dynastic, marketable: "America's Team."
Among their numerous loathsome qualities, one stood out above all others.
They kept winning.
Each undeserved victory made them more arrogant, more insufferable. To the point when you felt that surely - were there a God in heaven - he would make them suffer just to restore the faith of people like me.
But this didn't happen. They changed coaches and were champions again. They changed players, and still managed to cruise to victory.
Their players were criminals, their owner, the king of all assholes, but their fans didn't care so long as they could be part of a winning side.
Just thinking of the times they crushed my team over and over again still rankles.
---
So it is with Manchester United - in the game that they actually play with their feet - they are the bazillion-pound gorilla squatting atop the league table, spitting out the bones of lesser teams and giving the "up yours" to anyone not wearing their colors.
They've won the championship fifteen times, they've won the double, the triple - and damn near everything in sight.
They were purchased for 1.5 Billion dollars, they field one of the largest payrolls in Europe. Their wealth gives them access to anyone and they gobble up talent anywhere they find it. Any player who does well at the Euro championships will likely play for Man U the following season. Their bench could make a solid showing in any league in the world.
And I hate them. Because they win. Because their fans are insufferable when they win. But mostly because they are usually to blame for my teams not going home with the trophy.
Truth be told, there are a number of Man U players I'd respect, I just wish they'd come to their senses and play for a likable side.
Giggs, for example, is just quality all the time. His play is always impressive and his work ethic hasn't been affected by the fact that most everyone around him is a raging jerkwad.
You see Giggs get mad, but it's usually for a very good reason. You never see him fly off the handle and whine about a non-call the way you would see C. Ronaldo do a few seasons ago.
Ronaldo. Any year but this past one, I'd say he was the biggest waste of talent in the league. All that speed, buckets of talent and he'd spend most of his time diving to the ground and whining about being fouled. His playacting was especially pathetic when he played for Portugal in the last World Cup - I think even his countrymen were mad at him after that one. All this showboating and nothing to show for it.
This year, Ronaldo seems to have put his head down and do what he does best - make defenders look foolish. So I can't bitch about him being the personification of what I hate about Man U.
That honor falls to Wayne Rooney - a thick-bodied bully of a striker who was England's false hope in the last World Cup - A man who is the prototypical boorish, hotheaded thug that Man U haters like me conjure up just to stoke their seething hatred of the Red Devils.
Rooney's got skills, no question - but when he isn't doing terribly well, you can tell he's looking for someone else to blame: the ref, the defender, his teammates, or the imaginary foul that stopped his breakaway.
Whatever it is - it sure as hell isn't the fact that Rooney has been playing for shit lately. That couldn't be it.
So, I've been enjoying watching Rooney have an off year, even if Man U had surged ahead of everyone in the league. It was nice to see that Rooney was getting pissed off and handling it badly - like watching McEnroe or Nastassi self-destruct - it was fun.
Today Man U played my team - Arsenal. In the Gunner's new digs - and I'm hoping for a repeat of Arsenal's dazzling form against other teams. Man U is the evil empire, but surely God has them due for a comeuppance. Right? He wouldn't just be toying with me, right?
Kickoff.
Right off the bat, Arsenal isn't playing well. Man U blasts a few at the net and dominates the early possession. Worse - there's this really shameful playacting by Eboue to fool the ref into carding a Man U player. Disgusting.
Arsenal's on their heels for a good part of the first half, but show some signs of life here and there. They just aren't combining well, and Henry (while finally back from injury) is in lurk mode.
Fabregas, the Spanish phenom, is scrambling for all he's worth, but just isn't getting any traction. He's showing a lot of heart, chasing no-hope balls that show you he's trying, but he's wasting a lot of energy and looking rather young.
A scoreless half ends - Man U has the upper hand, but maybe Arsenal can start fresh after the half. I can hope right? How cruel can the universe be?
Second half.
Arsenal does come out with a bit more flare - and Man U gets pushed back and suddenly I'm getting hopeful.
Then Rooney does something he hasn't done in awhile: he scores.
Arsenal is down 0-1 to the forces of darkness, scored on by the foulest Red Devil of them all.
Man U's fans are in the house and they go ape. Arsenal tries to respond with a quick equalizer, but they are more desperate than skilled. Rosicky has made it his personal mission to whiff on as many easy ones as he can - three or four good chances will fall at his feet, and he'll blow them.
Twenty-two minutes in, Wenger sends in Van Persie- who is not in top shape. This smacks of desperation to me, but I'm looking for any hope I can get.
Twenty minutes to go, Arsenal are struggling hard, but long balls aren't going their way - passes that could be brilliant moves are intercepted and turned into counterattacks. Ronaldo is increasingly dangerous.
Eighty one minutes in, it looks like Man U has started the stall. They sub in Saha, and people are taking their time.
Adebayor keeps displaying more drive than sense by charging Van de Saar before every goal kick - like he's going to slip up. Yeah, Van de Saar. Screw up. Never gonna happen.
And Fabregas, he's just too young to know that this is going nowhere - he's sliding and diving and charging balls that are meaningless. Wild passes, wild shots - it's practically embarrassing.
He and Rosicky get into a scrum with two Man U defenders, and it looks like one of those basketball plays where the players keep falling over and you're just waiting to see who will get tagged with the foul.
--and then Fabregas gets the ball and nicely slips it to Rosicky-
--Rosicky jets into the box and crosses to Henry-
--who does an amazing backheel pass to
--Van Persie who blasts it past a diving Van de Saar.
Tied. Son of a bitch! Seven minutes from time and Arsenal gets to salvage a point in front of the faithful. Awesome. More than could be expected. Honor is served.
And then things get strange. Arsenal starts surging into attack mode - there's blood in the water, and you get the feeling that - time permitting - they may not be done.
Two good chances go nowhere, but Man U is clearly out of it now. Lots of hard work, but nothing approaching their earlier dominance.
Four minutes of injury time - and you know the Man U fans are sweating it. They're on the chopping block and it's clear - only the clock will save them.
And then there's a wild sequence of passing - Fabregas again, then away, then Eboue curls a cross into the pack and -
Henry soars up to head the cross into the net.
Pandemonium.
It'll go down as minute 90, but it's 92 and change. Man U has no time to salvage a point, although they try.
A driving shot goes to Lehmann, who almost stalls himself into a yellow card for delay. He boots the ball to midfield and the whistle blows.
Scoreline - January 23, 2007
Arsenal: 2
Manchester United: 1
Rooney 53, Van Persie 83, Henry 90
God is in his heaven.
Among their numerous loathsome qualities, one stood out above all others.
They kept winning.
Each undeserved victory made them more arrogant, more insufferable. To the point when you felt that surely - were there a God in heaven - he would make them suffer just to restore the faith of people like me.
But this didn't happen. They changed coaches and were champions again. They changed players, and still managed to cruise to victory.
Their players were criminals, their owner, the king of all assholes, but their fans didn't care so long as they could be part of a winning side.
Just thinking of the times they crushed my team over and over again still rankles.
---
So it is with Manchester United - in the game that they actually play with their feet - they are the bazillion-pound gorilla squatting atop the league table, spitting out the bones of lesser teams and giving the "up yours" to anyone not wearing their colors.
They've won the championship fifteen times, they've won the double, the triple - and damn near everything in sight.
They were purchased for 1.5 Billion dollars, they field one of the largest payrolls in Europe. Their wealth gives them access to anyone and they gobble up talent anywhere they find it. Any player who does well at the Euro championships will likely play for Man U the following season. Their bench could make a solid showing in any league in the world.
And I hate them. Because they win. Because their fans are insufferable when they win. But mostly because they are usually to blame for my teams not going home with the trophy.
Truth be told, there are a number of Man U players I'd respect, I just wish they'd come to their senses and play for a likable side.
Giggs, for example, is just quality all the time. His play is always impressive and his work ethic hasn't been affected by the fact that most everyone around him is a raging jerkwad.
You see Giggs get mad, but it's usually for a very good reason. You never see him fly off the handle and whine about a non-call the way you would see C. Ronaldo do a few seasons ago.
Ronaldo. Any year but this past one, I'd say he was the biggest waste of talent in the league. All that speed, buckets of talent and he'd spend most of his time diving to the ground and whining about being fouled. His playacting was especially pathetic when he played for Portugal in the last World Cup - I think even his countrymen were mad at him after that one. All this showboating and nothing to show for it.
This year, Ronaldo seems to have put his head down and do what he does best - make defenders look foolish. So I can't bitch about him being the personification of what I hate about Man U.
That honor falls to Wayne Rooney - a thick-bodied bully of a striker who was England's false hope in the last World Cup - A man who is the prototypical boorish, hotheaded thug that Man U haters like me conjure up just to stoke their seething hatred of the Red Devils.
Rooney's got skills, no question - but when he isn't doing terribly well, you can tell he's looking for someone else to blame: the ref, the defender, his teammates, or the imaginary foul that stopped his breakaway.
Whatever it is - it sure as hell isn't the fact that Rooney has been playing for shit lately. That couldn't be it.
So, I've been enjoying watching Rooney have an off year, even if Man U had surged ahead of everyone in the league. It was nice to see that Rooney was getting pissed off and handling it badly - like watching McEnroe or Nastassi self-destruct - it was fun.
Today Man U played my team - Arsenal. In the Gunner's new digs - and I'm hoping for a repeat of Arsenal's dazzling form against other teams. Man U is the evil empire, but surely God has them due for a comeuppance. Right? He wouldn't just be toying with me, right?
Kickoff.
Right off the bat, Arsenal isn't playing well. Man U blasts a few at the net and dominates the early possession. Worse - there's this really shameful playacting by Eboue to fool the ref into carding a Man U player. Disgusting.
Arsenal's on their heels for a good part of the first half, but show some signs of life here and there. They just aren't combining well, and Henry (while finally back from injury) is in lurk mode.
Fabregas, the Spanish phenom, is scrambling for all he's worth, but just isn't getting any traction. He's showing a lot of heart, chasing no-hope balls that show you he's trying, but he's wasting a lot of energy and looking rather young.
A scoreless half ends - Man U has the upper hand, but maybe Arsenal can start fresh after the half. I can hope right? How cruel can the universe be?
Second half.
Arsenal does come out with a bit more flare - and Man U gets pushed back and suddenly I'm getting hopeful.
Then Rooney does something he hasn't done in awhile: he scores.
Arsenal is down 0-1 to the forces of darkness, scored on by the foulest Red Devil of them all.
Man U's fans are in the house and they go ape. Arsenal tries to respond with a quick equalizer, but they are more desperate than skilled. Rosicky has made it his personal mission to whiff on as many easy ones as he can - three or four good chances will fall at his feet, and he'll blow them.
Twenty-two minutes in, Wenger sends in Van Persie- who is not in top shape. This smacks of desperation to me, but I'm looking for any hope I can get.
Twenty minutes to go, Arsenal are struggling hard, but long balls aren't going their way - passes that could be brilliant moves are intercepted and turned into counterattacks. Ronaldo is increasingly dangerous.
Eighty one minutes in, it looks like Man U has started the stall. They sub in Saha, and people are taking their time.
Adebayor keeps displaying more drive than sense by charging Van de Saar before every goal kick - like he's going to slip up. Yeah, Van de Saar. Screw up. Never gonna happen.
And Fabregas, he's just too young to know that this is going nowhere - he's sliding and diving and charging balls that are meaningless. Wild passes, wild shots - it's practically embarrassing.
He and Rosicky get into a scrum with two Man U defenders, and it looks like one of those basketball plays where the players keep falling over and you're just waiting to see who will get tagged with the foul.
--and then Fabregas gets the ball and nicely slips it to Rosicky-
--Rosicky jets into the box and crosses to Henry-
--who does an amazing backheel pass to
--Van Persie who blasts it past a diving Van de Saar.
Tied. Son of a bitch! Seven minutes from time and Arsenal gets to salvage a point in front of the faithful. Awesome. More than could be expected. Honor is served.
And then things get strange. Arsenal starts surging into attack mode - there's blood in the water, and you get the feeling that - time permitting - they may not be done.
Two good chances go nowhere, but Man U is clearly out of it now. Lots of hard work, but nothing approaching their earlier dominance.
Four minutes of injury time - and you know the Man U fans are sweating it. They're on the chopping block and it's clear - only the clock will save them.
And then there's a wild sequence of passing - Fabregas again, then away, then Eboue curls a cross into the pack and -
Henry soars up to head the cross into the net.
Pandemonium.
It'll go down as minute 90, but it's 92 and change. Man U has no time to salvage a point, although they try.
A driving shot goes to Lehmann, who almost stalls himself into a yellow card for delay. He boots the ball to midfield and the whistle blows.
Scoreline - January 23, 2007
Arsenal: 2
Manchester United: 1
Rooney 53, Van Persie 83, Henry 90
God is in his heaven.
Subscribe to:
Posts (Atom)