Saturday, December 30, 2006
My brother Dan suggested I look into network-attached storage for my file-server needs. Network-attached storage is a big hard drive that can be plugged in to a local area network and accessed from any local computer. (I keep trying to write that sentence in a way that would make sense to non-IT pros; did I succeed?) NAS boxes just barely start at around $250, and ones that are actually RAID's or are high-capacity are lots more than that, and I'd have to replace my router to get a fast enough network to make it worthwhile. Replacing my router is another coupla hundred dollars. Pondering all of this I remembered that I started this off by trading hardware I wasn't using for a new PC. "File server" is not one of the goals on my post-it notes on the window. I just don't want to spend hundreds of dollars on a file server right now. I would just like for my macs to stop running out of disk space every three days. Simple solution! I ordered a simple, external USB hard drive. I'll plug it into my mac mini, which will make a just fine file server for the windows box and the other mac. I'll be behind mac os x firewall goodness, I'll have superfast access from my main dev machine, and I won't have to rely on the windows file system. Sound okay?
we hate errands
Going to retail stores is soul-sucking, wallet-shrinking, and afternoon-destroying. And yet, I want more memory for my PC right now, and my desk chair has finally reached the point of not just being uncomfortable but actively causing back pain that lasts for hours. Ikea has a chair that I want; I've been chair-shopping for a year and have decided that Ikea's high-end task chair is the best ergonomic option for less than $300. Mail-ordering Ikea is stupid (insane shipping charges), but going there is such a production. I can order from Fry's and get delivery in four days (silly long weekend). Or I could just wait until I want memory enough to be willing to drive there and back. Nope, never happen, it's a 40 minute drive one way. Or I could just plain wait. Wealth comes from not spending money.
windows vista defeats high-quality content playback
A Cost Analysis of Windows Vista Content Protection by Peter Gutman is absolutely required reading for anyone considering buying Vista, or anyone who cares about media content quality. Holy crap. If this article can be believed, Windows Vista has content protection built in to the operating system such that any content or hardware or software that plays back "premium" media must automatically and silently degrade the content being played. The goal of the built-in content protection seems to be assuage the media business (film, tv, and music industries) and push consumers into an all-Microsoft end-to-end content solution. The effect of this built-in content protection will be that expensive content and hardware provides a crappy viewing experience. We're not just talking about a $200 graphics card looking like a $50 graphics card...we're talking about a thousands-of-dollars flat screen monitor playing back a $50 blu-ray dvd on a $2K computer, and having it look like a vhs tape on an old tv. Granted, I have not actually seen this effect in person, but I understand enough of signal processing to know that when you mess with a signal, you degrade it. It sounds like Vista will be messing with the signal at the encoding/decoding layer (which can be software or hardware) and at the hardware-output layer. Goodbye, signal quality. And yet! The worst of it! Most users won't know Vista is degrading their content. Most people put up with whatever performance their machine happens to give them. If it takes twenty minutes to boot the OS, or if their laptop screen always looks a little fuzzy, or if they always have to hit the print button three times to get it to print once, they just accept that as what the computer does, even when those effects could be fixed by defragmenting the hard drive, changing the screen resolution to match the native LCD resolution, or upgrading the printer drivers. That is, the performance of most users' machines are already far worse than the hardware is capable of, because of miscellaneous configuration problems outside the realm of their consideration. Vista is going to make this much, much worse. Before long, people will start to realize that a properly configured non-Windows box gives them far better media playback for the same hardware cost than this Vista eater-of-souls. Oh wait, isn't that a TiVo? Or a Slingbox? or a Mac Mini? I predict that by next year's holiday season there will be another round of booming linux distro-plus-services sales to rescue Vista machines from their content-protected hell. Insert this cd, restart, and watch your machine start acting like the three thousand dollars you spent on it. Provide users with a decent webmail solution and a way to edit the Word files from the office... and the world will beat a path to your door... but only if they can hear you over the sound of the Windows marketing.
Thursday, December 28, 2006
tools for porting to openlaszlo 4.0b1
On the Open Laszlo project blog, I describe tools for porting 3.x applications to 4.0b1. I am extremely tickled to report that this has been translated into French and German. The German version even has screengrabs. Thanks to Monsieur Patate and Raju Bitter for the translations. Apparently "Ça plante toujours?" and "Immer noch am kämpfen?" are translations for the conditional at the beginning of step 12.
Tuesday, December 26, 2006
national change your passwords day: schneier on passwords
Bruce Schneier, cryptography expert, recently appeared on NPR's Future Tense discussing what makes a good password, what makes a bad password, and how to manage passwords that are too random to remember. He recommends that you write your passwords on a piece of paper and put them in your wallet, along with the other valuable small pieces of paper you carry around: paper currency.
as if it weren't already clear that i am a mac fanboy
Last night I dreamt that it was the first day of macworld expo and I could finally see what Steve Jobs was going to announce at the keynote.
Sunday, December 24, 2006
holy crap!
Holy crap, life is good! Life is top-quality, best-ever good.
I spent the morning reading the first chapter of Mac OS X Internals: A Systems Approach, which traces the history of the operating systems that eventually became or influenced Mac OS X. All mac geek friends should read the first chapter of this book, or the extended version available online. The mega-cool things about Mac OS X were apparently developed twenty or thirty years ago. Protected memory, preemptive multitasking, microkernels, gigantic virtual memory spaces, vector graphics. To which I say: Holy crap!
God, it is such bliss to sit in my warm apartment with my cats and read really good technical books. It is such bliss to take a break from work. Green tea lattes. Financial security. Plans with friends for dinner. Financial security. (Yes, I said that twice.) The freedom to nap if I want to. Heat. Thumbs! Socks! Hats!
I spent the morning reading the first chapter of Mac OS X Internals: A Systems Approach, which traces the history of the operating systems that eventually became or influenced Mac OS X. All mac geek friends should read the first chapter of this book, or the extended version available online. The mega-cool things about Mac OS X were apparently developed twenty or thirty years ago. Protected memory, preemptive multitasking, microkernels, gigantic virtual memory spaces, vector graphics. To which I say: Holy crap!
God, it is such bliss to sit in my warm apartment with my cats and read really good technical books. It is such bliss to take a break from work. Green tea lattes. Financial security. Plans with friends for dinner. Financial security. (Yes, I said that twice.) The freedom to nap if I want to. Heat. Thumbs! Socks! Hats!
Saturday, December 23, 2006
signal to noise
A few days ago I sent a request to co-worker saying "please do XXX -- but not until friday." He handled the request immediately, and when I asked him about it, he said, "You think I read all your mail?" It would be ridiculous to complain about a request being handled too fast, and that this co-worker is way on top of his game, so probably the miscommunication came from me. I send so much email to internal and external team mailing lists that it is entirely understandable that a few important nuggets would occasionally be missed. Could I send less email and be a more effective team member?
Andy van Dam is legendary for his use of ultra-compact email replies:
With these eight-letter messages, Andy runs several small empires. What can I leave out of my email compositions to be more effective?
Andy van Dam is legendary for his use of ultra-compact email replies:
- tnx -a
- ack. -a and ok -a
- see me -a and its more intimidating cousins see me pls and call me.
- tmrw and do it and ask lsh are also frequent fliers.
With these eight-letter messages, Andy runs several small empires. What can I leave out of my email compositions to be more effective?
policies are useless
A few days ago I blogged about personal behavioral codes I call "policy," as in, "I have a policy that I don't talk on the phone while driving." The stupid thing, though, is that I sliced up the tip of my thumb while cutting rock-solid bread with a large but crappy knife. I didn't have an explicit policy "be careful when using knifes" but would it really have helped me? Of course I should be careful when using knives, but a policy about it would only provide an illusion of awareness. Like a mission statement: either you have a mission, or you don't. Putting a mission statement into words and up on the wall or for that matter tattooed on your wrist is no substitute for actually having a mission. Missions are felt and acted upon. Safety is a way of acting not just a policy. The most important conduct is how I act hours before a hard deadline, the day before going on vacation, before the sun is up, before I've had coffee, after a night of tossing and turning. "Policy" is how I think I should act, but "history" is how I do act. "Policy" is a comforting illusion.
Sunday, December 17, 2006
clean slate
I love a clean slate. I have gotten in several really bad conflicts with people over the last year or so in which I recommend starting over from a clean machine, they prefer another strategy, and I then refuse to have anything to do with their machines.
This behavior of mine is excessively rigid and decidedly non-agile. Why do I get so upset? Why do I get so upset over other people's computers?
Well, computers do accumulate cruft. (Yesterday a co-worker ran out of disk space on a fairly new macbook pro; he soon discovered that iMovie had been making duplicate copies of all of his videos. 30 gigs worth.) Cruft is nefarious and hard to detect, but it usually slows down the machine. Maybe you installed twenty dashboard widgets and forgot about them. Maybe you installed a system extension that looks up dictionary definitions for all words over eight characters. Maybe you turned on a "run real slow" option somewhere and forgot about it. On the PC, system degradation is often the result of malware. Then in a boiling-the-frog way, system performance degrades... until I sit down at your computer and freak out over how slow it's acting. "I have the same hardware / worse hardware and it's way faster than this." or "This machine is made of nice components; it should be faster than this." That assertion is very difficult to support with hard facts; it relies on my subjective experience of the hundreds of computers I've spent time with in the last twenty years. It doesn't matter if I'm right that the current machine performance is much worse than the hardware's ideal speed; it matters that the frog is just warm but not cooked. A warm frog and a slow-ish computer are not catastrophes for normal people.
Now, I could go off into self-justification here, and claim that I get so upset because of the future of doom that I foresee for a warm frog, and the machine/frog's owners coming stress and regret over a dead pet. That's not it, though. I get upset because I don't know how to save the frog. I don't know how to go from a slow-ish computer to a fast-ish computer. I don't know how to diagnose why a slow-ish computer is slow. My answer is always to start over, wipe the disk, and then the trouble goes away for a while. I think it's kind of fun to get a new environment set up on a clean machine; most people regard setting up a new environment on a clean machine as a major diversion from actually getting work done. And, in truth, people who let me wipe their machines usually end up with a set of new problems; not slow problems, but configuration problems. Most people will experience this as going from a warm frog to a paralyzed (albeit cool) frog... and when considering my recommended course of action, wiping the machine, they foresee the paralyzed frog, a computer which completely prevents them from accomplishing any of their tasks.
This explains the conflicts: we are both predicting doom as a result of following the other's recommendations, but our definition of doom is different. For me, a slowish computer right now is doom; for others, a slowish computer is preferable to an unconfigured computer. We have different values. And it's not my computer so I should keep my frog-related-fears to myself!
[Postscript: This has absolutely nothing to do with my reinventing my entire life every five years.]
This behavior of mine is excessively rigid and decidedly non-agile. Why do I get so upset? Why do I get so upset over other people's computers?
Well, computers do accumulate cruft. (Yesterday a co-worker ran out of disk space on a fairly new macbook pro; he soon discovered that iMovie had been making duplicate copies of all of his videos. 30 gigs worth.) Cruft is nefarious and hard to detect, but it usually slows down the machine. Maybe you installed twenty dashboard widgets and forgot about them. Maybe you installed a system extension that looks up dictionary definitions for all words over eight characters. Maybe you turned on a "run real slow" option somewhere and forgot about it. On the PC, system degradation is often the result of malware. Then in a boiling-the-frog way, system performance degrades... until I sit down at your computer and freak out over how slow it's acting. "I have the same hardware / worse hardware and it's way faster than this." or "This machine is made of nice components; it should be faster than this." That assertion is very difficult to support with hard facts; it relies on my subjective experience of the hundreds of computers I've spent time with in the last twenty years. It doesn't matter if I'm right that the current machine performance is much worse than the hardware's ideal speed; it matters that the frog is just warm but not cooked. A warm frog and a slow-ish computer are not catastrophes for normal people.
Now, I could go off into self-justification here, and claim that I get so upset because of the future of doom that I foresee for a warm frog, and the machine/frog's owners coming stress and regret over a dead pet. That's not it, though. I get upset because I don't know how to save the frog. I don't know how to go from a slow-ish computer to a fast-ish computer. I don't know how to diagnose why a slow-ish computer is slow. My answer is always to start over, wipe the disk, and then the trouble goes away for a while. I think it's kind of fun to get a new environment set up on a clean machine; most people regard setting up a new environment on a clean machine as a major diversion from actually getting work done. And, in truth, people who let me wipe their machines usually end up with a set of new problems; not slow problems, but configuration problems. Most people will experience this as going from a warm frog to a paralyzed (albeit cool) frog... and when considering my recommended course of action, wiping the machine, they foresee the paralyzed frog, a computer which completely prevents them from accomplishing any of their tasks.
This explains the conflicts: we are both predicting doom as a result of following the other's recommendations, but our definition of doom is different. For me, a slowish computer right now is doom; for others, a slowish computer is preferable to an unconfigured computer. We have different values. And it's not my computer so I should keep my frog-related-fears to myself!
[Postscript: This has absolutely nothing to do with my reinventing my entire life every five years.]
national "change your passwords" day
January 17th, 2007, is hereby declared as National Change Your Passwords Day. Get your tools together and get ready! There are dozens of password management tools, including a moleskin notebook. A low-tech strategy that has served me extraordinarily well is writing the accounts and passwords out longhand on paper, then laminating the paper, and storing it somewhere safe. For extra points, xerox that and put it in your safety deposit box with your passport and your offsite backups. (No, even I don't have a safety deposit box with offsite backups.) For casual passwording, I use the Mac OS X Keychain Access application. Once I used a Palm Pilot password vault, then discovered that sync'ing the application did not also sync the data. Whoops.
Over the next few weeks I will post more suggestions on getting psyched up for National Change Your Passwords day.
A parting thought: Over the past year, to how many people have you revealed a password? Common reasons for revealing a password include "I'm offline and I need that email message," "tech support needs to log in to my computer," and "my boyfriend's going to the ATM so he's getting cash for me too." Has your relationship with any of those people changed since you revealed a password? How about your relationship with any of the people who might have overhead that conversation? If your passwords were compromised, how much money could an evildoer steal from you in one day?
Over the next few weeks I will post more suggestions on getting psyched up for National Change Your Passwords day.
A parting thought: Over the past year, to how many people have you revealed a password? Common reasons for revealing a password include "I'm offline and I need that email message," "tech support needs to log in to my computer," and "my boyfriend's going to the ATM so he's getting cash for me too." Has your relationship with any of those people changed since you revealed a password? How about your relationship with any of the people who might have overhead that conversation? If your passwords were compromised, how much money could an evildoer steal from you in one day?
Saturday, December 16, 2006
"offered without comment" is a way of commenting
The Microsoft Wireless Comfort Keyboard drivers have not passed Microsoft Windows Logo Testing.
powered by performancing firefox
towards a better open laszlo install procedure
I installed glassfish on my pc yesterday. Glassfish is a shiny new j2ee server; I am evaluating it as a replacement for tomcat 5.0.30, which is dying a few times a day in one installation I monitor. The glassfish installation process was beautiful: an executable jar did it all, and got it right the second time. (I had to configure my path to get to a JDK first, not a JRE.) Next I downloaded a recent Open Laszlo servlet war, dropped it into glassfish's auto_deploy directory, then, poof, my servlet was installed. (Anybody want more detailed instructions on deploying Open Laszlo to glassfish? Comment here.)
That same day, one of the hardcore Open Laszlo developers mentioned the emotional fortitude necessary to create a cygwin build and development environment; earlier that I day, I completely blew up at two very skillful people creating a new development environment on a mac. Earlier this week, my team was temporarily unable to create Windows installers for Open Laszlo because of a hardware failure on the one PC that we use to build NSIS installers.
The problem here is not the operating systems, the source code, the hardware, nor (least of all!) my co-workers. The problem is the Open Laszlo build process, for which I am culpable, and the Open Laszlo install process, which has been on my plate to improve for months now.
My goal: make it possible to install an Open Laszlo server using a pure-Java installer which is almost entirely identical for windows, mac, and linux. And: make it possible to create an Open Laszlo/subversion build environment in less than an hour (after getting all the binaries), without suffering, without hand-editing a bashrc, and without worrying about forward-slash vs backward slash.
That same day, one of the hardcore Open Laszlo developers mentioned the emotional fortitude necessary to create a cygwin build and development environment; earlier that I day, I completely blew up at two very skillful people creating a new development environment on a mac. Earlier this week, my team was temporarily unable to create Windows installers for Open Laszlo because of a hardware failure on the one PC that we use to build NSIS installers.
The problem here is not the operating systems, the source code, the hardware, nor (least of all!) my co-workers. The problem is the Open Laszlo build process, for which I am culpable, and the Open Laszlo install process, which has been on my plate to improve for months now.
My goal: make it possible to install an Open Laszlo server using a pure-Java installer which is almost entirely identical for windows, mac, and linux. And: make it possible to create an Open Laszlo/subversion build environment in less than an hour (after getting all the binaries), without suffering, without hand-editing a bashrc, and without worrying about forward-slash vs backward slash.
powered by performancing firefox
Thursday, December 14, 2006
entomology == etymology
Entomology and etymology could be used interchangeably if you are talking about whether to call a bug "P0" or "P1" and whether LPP-3231 is the same as LPP-3033, and where we got the acronym LPP for Open Laszlo bugs.
Friday, December 01, 2006
real-time collaborative problem solving
I left work early to have time to walk along the ocean while the sun was still up. As I walked south along the sea wall, the pier eclipsed the sun. I saw a seagull limping oddly at the beach at the foot of the pier. I thought it was just injured, until I saw the straight, thin lines extending in the air from the bird up to the pier. Fishermen stood sillhouetted against the sky. A woman walking the other direction paused and said to me, "It's a shame. The bird's got a hook caught in it. It's a death sentence." I realized a boy was climbing down the seawall to free the bird, which was almost as big as he was. After watching for a minute, I said, "I'm going down there." The woman standing next to me said, "I would but I'm wearing leather clogs." I looked at her in a tidy corduroy blazer and slacks, then down at my sneakers, bought for $150 back when I thought I could afford such things, but now much worse for the wear. "Don't ruin your shoes," I said to her. "Can you do it, just you and the boy?" she asked. "We can do it. You don't have to come.""Hold on, kiddo, we're coming down there," she called to the boy, who had backed the gull against the pier's rusted metal base.
When I got to him he said to me, "I don't want to touch her." I didn't, either. I felt vulnerable and soft, could imagine the frightened bird squirming in my arms, scratching me, wings beating in my face, more horror. The woman with me said, "Don't cut the line. If you cut the line, the hook will stay in it, and it'll be a death sentence." In the back of my mind I thought about this: is a fishhook stuck in a gullwing a death sentence? Not necessarily, but maybe; it depends on where we cut the line and whether the hook had punctured her skin. The bird was actually caught in two lines. I pulled on one of them, felt the flexing fishing pole it was attached to, and called out for slack. We would need slack to do anything at all for the bird; if we cut the line while it was under tension, we'd have no control over the fragment attached to the bird. I held onto the line a few feet from the bird, reached out to gather up the other line and take the tension off the bird, and paused to consider the technical questions.
At this point the mood changed. The older woman began to harangue the men on the pier for a knife. Yes, harangue. I couldn't understand what the men were saying; they were just shadows against the bright sky. A woman wearing fleece and sunglasses leaned over the railing of the pier and called down, "don't cut the line. we're going to get scissors." I thought that scissors sounded great, but I didn't want to wait some unknown amount of time for scissors to appear. I decided to see if my keys could cut one of the lines. The woman beside me kept issuing instructions, but I honestly wasn't listening. I think a few times she said, watch out for the water, meaning that a wave was coming in. I mumbled, "that doesn't matter," not selflessly, but just wanting to ellide the problem of paying attention to the surf. There seemed to be an argument about how best to proceed. The serrations on my keys couldn't fray the nylon line; in the back of my mind I realized, this is why one should always carry a knife. I longed for my leatherman. "Don't leave the hook in!" the two women called out. "You've got to get the hook out!" Then their chorus changed. "He says his girl is coming down," one of them announced, and indeed I saw a young woman begin to pick her way down the rocks. The coming of the girl seemed to be considered by the men on the pier to be a complete and perfect solution; I was curious as to how she was going to fix the situation. Perhaps she was carrying scissors or a knife.
While she climbed down the rocks, another shouted conversation emerged; the woman on the beach with me was sarcastically repeating the fishermen's claim that the bird got stuck in the line all the time. "Yeah, right, he gets stuck in the line all the time!" she mocked. I didn't understand this, either. The same bird? What on earth was she talking about? I think what the fishermen meant is that a seagull stuck in their lines is not such a rare occurrence and not a cause for panic.
Indeed, the young woman knew exactly what to do. She used a rag she was carrying to cover and then wrap the bird's head; the bird stopped flapping. Now we had a topology problem, not a wildlife problem. This, I knew how to cope with. I passed the two lines, which I still held, to the older woman. "Take this" I said. "Hold this." Apparently my keys were in my hand, too, because she took those first. "Take the lines." I pressed them into her hands. I needed her to keep the lines slack, and I needed both my hands free. Then the girl and I knelt beside eachother in the sand and tracked the lines around the body, untangled the lines from the birds legs. To slide it underneath her, I pulled the line into the wet sand. I still didn't want to touch her much, but the girl held the bird's head in the rag and deftly extended its wings. Almost without words, we unwound loop after loop. She could tell that I didn't want to touch the bird much, so she did, gesturing with her chin and eyes at the next knot we should tackle. Two, three, six times the line was looped around the bird. The woman on the beach behind the girl and I asked, "should I hold her down? should I pick her up so you can get around her?" "No," I mumbled again, as the girl and I passed the tangles, bird, and sand back and forth between us.
Finally the line was almost free, disappearing into the bird's wing in the large flight feathers at what would have been her elbow. In my head I was picturing a bat skeleton, because I know bats better than I know birds. The hook might have been sunk into the flesh of her wing, or the line might be simply looped around the bone. Here again I didn't know how to proceed; I didn't know the shape of the hook, or how big it was, and I was not going to poke my finger into the squirming feathers to find out. I was definitely not willing to cut my hand on the hook in blind exploration, so again, I paused to consider the technical issues. I briefly imagined a cut finger infected with bird germs, which reinforced my desire not to find the hook by touch. The fishermen's daughter saw to the heart of it, though; the lines entered the wing feathers in two places. The hook was a few feet up the line, already controlled by the other woman holding the lines for slack. She held the wing open while I loosened the loop and finally freed the wing. I think there was another pause then; the girl gestured that I should step back, and she stepped back, and released the bird and the hood, at once. The bird flew away; I did not see it go.
I didn't know what to say to the girl who had held the bird and extended its wing. She had been so skillful and fearless. The bird would not have been freed if not for her. For just a moment I saw her skin glow in the red sunlight, saw her hair in the wind, saw her eyes shining; she climbed up the rocks and was gone.
The older woman in the clogs and corduroy was still talking; I began to understand that this adventure was part of a long narrative for her, of a small town homeowner resentful at the men who came daily to her neighborhood to fish from the pier. "They didn't want us to cut the line because they were so concerned with their precious fishing line." This was ridiculous; I pictured in my head spool after spool of fishing line on a rack in a store, and knew that a few meters of line would cost only pennies. "That's why they wouldn't give us a knife," she continued. "They were going to let it die." And then, strangest of all, she said, "I was saying 'don't cut the line' because I wanted you to cut it closer to her body so you could take the hook out. I didn't mean you should leave the line in her." In the same breath that she justified the instructions she had issued, she criticized the fishermen's motives for advocating the very same plan. She cared about the bird, in a save-the-wholes kind of way, but she had no immediate solutions to help it. She made plans and gave instructions, while actually doing nothing, until a task was literally thrust into her hands. When it was over she couldn't say, well done, or I'm so glad the bird is free; instead she went immediately to criticizing others. I asked her, "Do you see the bird? Did it fly away all right?" "Yes," she said. "I saw it leave." I found my footing atop the seawall and walked away, dirty hands, sand in my shoes, feeling for once my body as a useful physical implement and not simply a container for my soul.
When I got to him he said to me, "I don't want to touch her." I didn't, either. I felt vulnerable and soft, could imagine the frightened bird squirming in my arms, scratching me, wings beating in my face, more horror. The woman with me said, "Don't cut the line. If you cut the line, the hook will stay in it, and it'll be a death sentence." In the back of my mind I thought about this: is a fishhook stuck in a gullwing a death sentence? Not necessarily, but maybe; it depends on where we cut the line and whether the hook had punctured her skin. The bird was actually caught in two lines. I pulled on one of them, felt the flexing fishing pole it was attached to, and called out for slack. We would need slack to do anything at all for the bird; if we cut the line while it was under tension, we'd have no control over the fragment attached to the bird. I held onto the line a few feet from the bird, reached out to gather up the other line and take the tension off the bird, and paused to consider the technical questions.
At this point the mood changed. The older woman began to harangue the men on the pier for a knife. Yes, harangue. I couldn't understand what the men were saying; they were just shadows against the bright sky. A woman wearing fleece and sunglasses leaned over the railing of the pier and called down, "don't cut the line. we're going to get scissors." I thought that scissors sounded great, but I didn't want to wait some unknown amount of time for scissors to appear. I decided to see if my keys could cut one of the lines. The woman beside me kept issuing instructions, but I honestly wasn't listening. I think a few times she said, watch out for the water, meaning that a wave was coming in. I mumbled, "that doesn't matter," not selflessly, but just wanting to ellide the problem of paying attention to the surf. There seemed to be an argument about how best to proceed. The serrations on my keys couldn't fray the nylon line; in the back of my mind I realized, this is why one should always carry a knife. I longed for my leatherman. "Don't leave the hook in!" the two women called out. "You've got to get the hook out!" Then their chorus changed. "He says his girl is coming down," one of them announced, and indeed I saw a young woman begin to pick her way down the rocks. The coming of the girl seemed to be considered by the men on the pier to be a complete and perfect solution; I was curious as to how she was going to fix the situation. Perhaps she was carrying scissors or a knife.
While she climbed down the rocks, another shouted conversation emerged; the woman on the beach with me was sarcastically repeating the fishermen's claim that the bird got stuck in the line all the time. "Yeah, right, he gets stuck in the line all the time!" she mocked. I didn't understand this, either. The same bird? What on earth was she talking about? I think what the fishermen meant is that a seagull stuck in their lines is not such a rare occurrence and not a cause for panic.
Indeed, the young woman knew exactly what to do. She used a rag she was carrying to cover and then wrap the bird's head; the bird stopped flapping. Now we had a topology problem, not a wildlife problem. This, I knew how to cope with. I passed the two lines, which I still held, to the older woman. "Take this" I said. "Hold this." Apparently my keys were in my hand, too, because she took those first. "Take the lines." I pressed them into her hands. I needed her to keep the lines slack, and I needed both my hands free. Then the girl and I knelt beside eachother in the sand and tracked the lines around the body, untangled the lines from the birds legs. To slide it underneath her, I pulled the line into the wet sand. I still didn't want to touch her much, but the girl held the bird's head in the rag and deftly extended its wings. Almost without words, we unwound loop after loop. She could tell that I didn't want to touch the bird much, so she did, gesturing with her chin and eyes at the next knot we should tackle. Two, three, six times the line was looped around the bird. The woman on the beach behind the girl and I asked, "should I hold her down? should I pick her up so you can get around her?" "No," I mumbled again, as the girl and I passed the tangles, bird, and sand back and forth between us.
Finally the line was almost free, disappearing into the bird's wing in the large flight feathers at what would have been her elbow. In my head I was picturing a bat skeleton, because I know bats better than I know birds. The hook might have been sunk into the flesh of her wing, or the line might be simply looped around the bone. Here again I didn't know how to proceed; I didn't know the shape of the hook, or how big it was, and I was not going to poke my finger into the squirming feathers to find out. I was definitely not willing to cut my hand on the hook in blind exploration, so again, I paused to consider the technical issues. I briefly imagined a cut finger infected with bird germs, which reinforced my desire not to find the hook by touch. The fishermen's daughter saw to the heart of it, though; the lines entered the wing feathers in two places. The hook was a few feet up the line, already controlled by the other woman holding the lines for slack. She held the wing open while I loosened the loop and finally freed the wing. I think there was another pause then; the girl gestured that I should step back, and she stepped back, and released the bird and the hood, at once. The bird flew away; I did not see it go.
I didn't know what to say to the girl who had held the bird and extended its wing. She had been so skillful and fearless. The bird would not have been freed if not for her. For just a moment I saw her skin glow in the red sunlight, saw her hair in the wind, saw her eyes shining; she climbed up the rocks and was gone.
The older woman in the clogs and corduroy was still talking; I began to understand that this adventure was part of a long narrative for her, of a small town homeowner resentful at the men who came daily to her neighborhood to fish from the pier. "They didn't want us to cut the line because they were so concerned with their precious fishing line." This was ridiculous; I pictured in my head spool after spool of fishing line on a rack in a store, and knew that a few meters of line would cost only pennies. "That's why they wouldn't give us a knife," she continued. "They were going to let it die." And then, strangest of all, she said, "I was saying 'don't cut the line' because I wanted you to cut it closer to her body so you could take the hook out. I didn't mean you should leave the line in her." In the same breath that she justified the instructions she had issued, she criticized the fishermen's motives for advocating the very same plan. She cared about the bird, in a save-the-wholes kind of way, but she had no immediate solutions to help it. She made plans and gave instructions, while actually doing nothing, until a task was literally thrust into her hands. When it was over she couldn't say, well done, or I'm so glad the bird is free; instead she went immediately to criticizing others. I asked her, "Do you see the bird? Did it fly away all right?" "Yes," she said. "I saw it leave." I found my footing atop the seawall and walked away, dirty hands, sand in my shoes, feeling for once my body as a useful physical implement and not simply a container for my soul.