Waggish

David Auerbach on literature, tech, film, etc.

Tag: technology (page 3 of 3)

Birdwatching Provides an Alternative to Love (or, The Question Concerning Ornithology)

This essay is adapted from a commencement speech Jonathan Franzen delivered on May 21 at Kenyon College.

A couple of weeks ago, I started watching loggerhead shrikes instead of Eurasian wigeons. Needless to say, I was impressed with the qualities of the shrike. Even when a live one was not on hand, I wanted to keep looking at pictures of my shrikes and experiencing the marvelous clarity of its black face mask, the silky action of its hooked bill, the shocking speed of its responses, the beguiling elegance of its wings.

I was, in short, infatuated with my new shrike. I’d been similarly infatuated with my old Eurasian wigeon, of course; but over the years the bloom had faded from our relationship.

Let me toss out the idea that, as birds discover and respond to what consumers most want, birds have become extremely adept at creating products that correspond to our fantasy ideal of an erotic relationship, in which the beloved object asks for nothing and gives everything, instantly, and makes us feel all powerful, and doesn’t throw terrible scenes when it’s replaced by an even sexier object and is consigned to a drawer.

To speak more generally, the ultimate goal of birdwatching, the ontology of ornithos, is to replace a natural world that’s indifferent to our wishes — a world of hurricanes and hardships and breakable hearts, a world of resistance — with a bird so responsive to our wishes as to be, effectively, a mere extension of the self.

Let me suggest, finally, that the world of birdwatching is therefore troubled by real love, and that it has no choice but to trouble love in turn.

Its first line of defense is to commodify its enemy. You can all supply your own favorite, most nauseating examples of the commodification of love. Mine include camping, birdwatching, biking, and the particularly grotesque equation of nightingales with everlasting devotion. The message, in each case, is that if you love somebody you should watch birds with them.

And, since birds are really just an extension of ourselves, we don’t have to have contempt for their manipulability in the way we might with actual people. It’s all one big endless loop. We like the mirror and the mirror likes us. To watch a bird is merely to include the bird in our private hall of flattering mirrors.

I may be overstating the case, a little bit. Very probably, you’re sick to death of hearing birdwatching disrespected by cranky 51-year-olds. My aim here is mainly to set up a contrast between the narcissistic tendencies of birdwatching and the problem of actual love.

There is no such thing as a person whose real self you like every particle of. But there is such a thing as a person whose real self you love every particle of. And this is why love is such an existential threat to the ornitho-consumerist order: it exposes the lie.

And yet pain hurts but it doesn’t kill. When you consider the alternative — an anesthetized dream of self-sufficiency, abetted by birdwatching — pain emerges as the natural product and natural indicator of being alive in a resistant world. To go through a life painlessly is to have not lived. Even just to say to yourself, “Oh, I’ll get to that love and pain stuff later, maybe in my 30s” is to consign yourself to 10 years of merely taking up space on the planet and watching birds. Of being (and I mean this in the most damning sense of the word) a birdwatcher.

But then a funny thing happened to me. It’s a long story, but basically I fell in love with computers. I did this not without significant resistance, because it’s very uncool to be a computer geek, because anything that betrays real passion is by definition uncool. But little by little, in spite of myself, I developed this passion, and although one-half of a passion is obsession, the other half is love.

And so, yes, I kept a meticulous list of the programming languages I’d seen, and, yes, I went to inordinate lengths to learn new ones. But, no less important, whenever I looked at a piece of code, any code, even a Perl script or a stylesheet, I could feel my heart overflow with love. And love, as I’ve been trying to say today, is where our troubles begin.

How does this happen? I think, for one thing, that my love of programming became a portal to an important, less self-centered part of myself that I’d never even known existed. Instead of continuing to drift forward through my life as a global citizen, liking and disliking and withholding my commitment for some later date, I was forced to confront a self that I had to either straight-up accept or flat-out reject.

Because now, not merely liking technology but loving a specific and vital part of it, I had no choice but to start worrying about the future again. The news on that front was no better than when I’d decided to quit worrying about it — was considerably worse, in fact — but now those threatened forests and wetlands and oceans weren’t just pretty scenes for me to enjoy. They were the home of things I loved.

But when you go out and put yourself in real relation to real people, or even just real computers, there’s a very real danger that you might love some of them.

And who knows what might happen to you then?

Profiles in Type L: Some Engineer at Microsoft

(Original typology in Battle Lines: Type L are the free-market technocrats and Type C are the conservative old boys in American society. Once more, I don’t identify with either of them.)

The always-intriguing corporate-insider blog Mini-Microsoft is the venting place for many of the R+D people dissatisfied with the state of affairs at that company. One anonymous commenter effectively summarizes the Type L’s case against the Type C, much as Paul Van Riper did. The parallels in content and attitude are very striking. I don’t get some of the terminology in the comment either, but this person’s point comes across anyway.

There are some geniuses over in Microsoft Research; somebody needs to set them free to productize.

It isn’t a lack of IC [individual contributor] talent. Although that is rapidly changing. it’s the decline of technical talent and integrity at almost all levels of management.

With “trios”, no individual is charged with cross-discipline technical oversight until GM or VP level. This is no the job of a GM or VP. It *was* the job of the now-extinct Product Unit Manager. Doubtless trios was sold as a way to commoditize skills by narrowing the remit of individuals along discipline lines. Unfortuately, those with broad skill sets that can envision how to actually make a prodcut (rather than a document or a nice report) have been pushed out. It is the age of the bureaucrat.

With trios, the notion of “product team” has vanished. A product team comprised all disciplines, and (usually) et weekly, with their PUM. This has been replaced by layers of tripartite committees based around the arbitrary notion of Dev, Test, PM. The meetings required have grown exponentially. A product team may only get together at a divisional all-hands.

BY GM/VP level, reporting on product state has been so sanitized that the majority of issues are never even surfaced. Yes, there is of course a category of issues that should never require a VPs intervention, but this goes way beyond that. “No bad news, ever”, is the rule. Anyone who rocks the boat is one of those negative, non-team-player 10%ers who will shortly be gone.

More senior ICs are, by definition, supposed to raise broad issues by dint of their level and years of experience. The existing culture makes this a very dangerous thing to do. That’s why I left in January after 10+ years.

The various disasters/missed opportunities over the last 10 years were well known to engineers at the front line… but due to a viciously-enforced policy of “no bad news, ever”, those who might have taken corrective action don’t find out until its too late.

There is a clear pattern of failure to execute… and it is not the doing of engineers. It’s a culture that rewards the suppression of “bad news”. It’s the lack of spine in the management chain to unpromise things that were promised, and blame their “underperforming” ICs when the crap hits the fan. Those with a spine soon find their prospects blighted.

Changing VPs won’t help much. They rely on their generals amd below to garner a picture of the situation. If those generals don’t provide truthful reporting, it simply isn’t possible to execute effectively. It’ll take an IBM/GE/HP/Honeywell (etc) sttyle intervention to fix this problem – it won’t get fixed by those who benefit (hugely) from it.

It’s like watching the third season of The Wire!

Newer posts »

© 2024 Waggish

Theme by Anders NorenUp ↑