Feeds:
Posts
Comments

Archive for the ‘journalism’ Category

SourceForge, the company for which I do most of my writing, was one of the pioneers of community-building on the web. Slashdot, one of its main sites, is notorious for both the size of its audience and its — well, frankness, I suppose. Linux.com, the site which publishes my work most often, is more subdued, but feuds still break out from time to time — and sometimes article links are posted on Slashdot, exposing me to even more fire. So, over the last few years, I’ve learned to live with the fact that my work will be discussed publicly and with no holds barred.

On the whole, I’ve been handled more generously than many of my colleagues. Nobody has ever threatened me, questioned my sexual orientation, or called me a communist (I probably would have insisted that I was an anarcho-syndicalist, and invoked the peasant commune in Monty Python and the Holy Grail if they had).

However, I have been called a “moron” and “ignorant” and been told that I wasn’t a real journalist. Memorably, too, reporting on an issue that involved three parties got me accused of being a paid hack for all three (I only wish I were, I might have said; I’d probably be much better paid).

And I’ve lost track of the times that people have missed my incorrigible if sometimes dry sense of humor, taken something I said out of context, or seen bias because I ventured to criticize a project or cause that was dear to them or seen proof of an opinion that was the dead opposite of the one I was expressing. I don’t very much mind being publicly berated — it goes with the job — but if I’m going to be verbally abused, I would prefer it was for something I actually said. Sometimes, I wonder if people have read my article at all.

At times, these misunderstandings seemed willful, as if those who made them were picking a fight out of frustration with something else in their lives, or were just waiting for an article vaguely related to a subject that they wanted to rant about. But eventually, I learned to take them in stride, and they cured me, too, of taking an undue pride in the compliments that I receive. After all, if the hostile comments were so far off-base, how could I suppose the friendly ones were any more accurate?

Some online journalists never read comments on their articles. However, even after I became disillusioned with them, I still continued to scan them at least. Between the extremes, there are also people with insights that hadn’t occurred to me, or with an expert knowledge or sharp eyes who point out genuine mistakes. I know I’m not infallible. I figure that I might as well take advantage of the comments to to rewrite an unclear sentence or two when necessary or correct a genuine factual error. After all, the ability to receive input and correct mistakes are two of the benefits of online journalism.

Still, I take a perverse pride in both the attacks and praises. If nothing else, they prove that my articles are at least being noticed. About six months ago, I posted a kudos and an abuse page on my website, and occasionally I read both of them together or add a comment to one of them. I find that they help to keep me from taking myself seriously when I should be taking the work seriously instead.

Read Full Post »

VA Software and the Open Source Technology Group, for whom I do most of my writing, are changing their name to SourceForge after their most successful web page. As part of the change, we’re getting new business cards – even the long-term contractors like me. The news has got me thinking about the whole idea of business cards, and my experience with them.

I suppose that business cards evolved out of the calling cards used in polite society in the nineteenth century. But where calling cards have fallen out of use, business cards continue to thrive, even in these days of the Internet. Attempts to replace them with mini-CDs for people with portfolios have never really caught on, although in some geek circles, such as the Debian Project, people sign each others’ public encryption keys instead of exchanging cards.

In Japan, I hear secondhand, there is an elaborate etiquette to giving and receiving cards, and even in North America, the exchange is ritualistic. I call it the business equivalent of two dogs sniffing each other’s butts – an analogy that, all humor aside, is not too far off, since both are greeting rituals. The cultures and customs are different, that’s all (It’s just as well that they are: wool and linen, the usual stuff of suits, preserve body odors even from a couple of meters away. You don’t really want to get that close to a lot of people).

Moreover, just as meeting dogs are evaluating each other’s status, a business card tells what level of access to a company you represent. People want to know if you have the power to make a deal, influence hiring decisions, or whatever else they might want from you. That’s why, at the startups I’ve been at, business cards suddenly start appearing as the company creeps out of stealth mode and starts interacting with other companies.

Of course, the appearance of business cards can also herald a rush for the status of grandiose titles in a company. Just getting a card is a sign of belonging, but, often, the ambitious want more.

I admit that I had some ego gratification when, after six months at a company, I suddenly found that I was director of marketing and communication, but, often, these titles mean remarkably little. In practice, I rather admire those who undermine the tradition, like the webmaster who liked to use Zope and had “Zopista” on his card, or the owner of a small company who listed himself as “CEO and Janitor.” I suppose that people who find these deviations annoying have a point, since not playing the game can obscure your level of clout, which is what people really want to know. However, at the same time, creative titles can be a talking point to strike up a conversation at a networking event, so they are more than just whimsy.

Business cards also create a first impression, which makes the frequent poorly designed ones out there all the more puzzling. The lowest levels of mediocrity are those printed from a template in a word processor on to a label sheet. Often, you can still see the perforations, and the designs are always uninspiring. But plenty of large companies issue cards that are almost as unimaginative. Perhaps that’s a subtle form of boasting, suggesting that a company doesn’t need a memorable card because it’s memorable in itself, like the mediocre advertising from megacorporations like McDonalds and Microsoft.

I’ve always preferred cards that have a dash to them, on the grounds that, if they are memorable, I’m more likely to be. I’ve designed a number of them, both for me and other people, and they always represent an interesting challenge in design, since they require standard information in a limited space that leaves little room for originality. My approach has always been to minimalize the information, and to add a checklist on the back, so that people can remember why they took a card and if they’re promised any followup action.

Since I started working chiefly as a journalist a couple of years ago, I haven’t bothered with a card. Most of the time, I’m contacting people via email or telephone rather than in person, and, if they want to know me, at any given time, they can find somewhere between fifty and one hundred thousand entries for me in a search engine. I had thought, though,of doing up a card to look like a bar code as a comment on the whole idea of business cards and their all-too common blandness. Now, it looks like I won’t have to bother.

The only thing that worries me is that, in the past, I’ve always moved on within a year after I received cards. Not that I am superstitious (he says, rapping his computer desk), but I hope that doesn’t happen with SourceForge.

Read Full Post »

A couple of weeks ago, I wrote an article about the closure of Progeny, a company for which I used to work. Usually, I lack the patience for nostalgia by temperment. Besides, experiences such as my high school reunion last fall have convinced me that such efforts are largely pointless. However, writing the article required contacting old acquaintances, and I became introspective, writing a reminiscence on my Linux Journal blog about working for Progeny and a sequel about Stormix Technologies, the company I worked at before Progeny.

Both, I realized, were part of the path to my current work as a journalist. After writing those articles, it strikes me more strongly than ever that my work history amounts to a circling around my core skills until I actually had the courage to use them.

In school and university, I never worried much about what I would do with my education. I have always been a firm believer in the value of learning for its own sake, and I was too interested in my classes to think much about where I was going. I always had vague plans about being a writer, but I can’t say that I took many concrete steps towards that goal – certainly not any consistent ones, anyway. As a result, I have a work history that might politely be described as chequered. Less polite observers would call it a thing of rags and patches that they wouldn’t even wear to wash the car on Sundays.

After I finished my bachelor’s degree, I literally had no idea what I wanted to do. I had taken a double major, straight out of high school with no more than a semester’s break, and I was mentallly exhausted. I took a minimum wage job in a bookstore to pay my share of the expenses, but it was a nightmare – not just because I endured a Christmas in which every second album played in the mall was the Smurf’s, but because I had never been previously exposed to the idea of books as commodities. Nor was I cut out for dealing with customers arriving one minute after closing or saying things like, “I can’t remember the title or the author, and I can’t explain what the book is about, but it’s got a green cover.”

Seeking escape, I entered graduate school. After all, what else does someone with an English degree do except teach? Besides, it was another few years in which I could put off the decision, and, meanwhile, I was at least talking about books as books.

I had given poetry readings and lectures at my old high school, thanks to the courtesy of Allan Chalmers, my Creative Writing Teacher. However, it wasn’t until I started working as a teaching assistant during my degree that I realized that I had a talent as a teacher. I enjoyed sharing my enthusiasms, and genuinely felt that I was helping students, if only by teaching them enough about writing to survive the rest of the university years.

That belief was enough to propel me through my years as a grad student and for another seven as a sessional instructor. I might not have been doing much writing myself, but at least I was talking about books.

But university English departments aren’t about enjoying literature. They’re about dissecting it, and, as I settled into semi-regular work, I realized that my distaste for straightjacketing literature into the latest trendy theory was counting against me in my struggle for full-time employment. My thesis supervisor and I described ourselves as the department’s “token humanists.” And I started thinking a lot about Robert Graves’ story of his oral defence, in which one professor said that he seemed like a well-read young man, but that he had a serious problem: He like some works better than others.

After seven years, I had squeezed the last hopes out of academia like an old lemon. I attended a presentation about technical writing, and jumped careers. It wasn’t the sort of writing that I wanted to do, but getting paid for writing sounded fine to me. No one cared, either, if I was a post-modernist or post-colonialist. The only priorities were accuracy and meeting deadlines, and since I’ve always been a first rate researcher and well organized, neither was a serious problem. Within six months, I had so much work that I was hiring sub-contractors, and was organizing major projects for international companies.

Unfortunately, I was also mind-thumpingly bored. In desperation, I learned typography so that my working life would have an element of creativity. I branched out into marketing and PR. I became ferociously devoted to learning the technologies I was documenting – not just enough to get by, the way that other writers did, but becoming an expert in them. Boredom receded, but it was still lapping at the outer edges of my mind.

That changed when I worked at Stormix and Progeny and discovered the joys of both free and open source software (FOSS) and of management responsibility. FOSS triggered my latent idealism, as well as my growing impatience with the average executive I met. When those jobs ended and I returned to being a technical writing consultant, boredom came flooding back. Only now, it was combined with a impatience at the mediocrity of those giving me orders.

With growing desperation, I realized that I didn’t care if the projects I was working on finished on time. Nor did anyone, else, really. Without a prospect in sight, I quit my last consulting job and started doing FOSS journalism. And, to my surprise, it seemed to be what I had wanted to do all along. It’s already lasted three years – about two years longer than any full-time employment I’d had since I went back to grad school – and I don’t think I’ll be tiring of it in a hurry.

That revelation may have seemed like a blinding flash of the obvious. However, I don’t think I could have done it sooner. I didn’t have the experience to know what I wanted or could do. I needed the experience of teaching to understand that I needed meaning in my work, and the experience of technical writing to believe that I could make a sustained effort in my writing. And, when I discovered FOSS, I also found a cause that I wanted to write about.

Looking back, I wish that I could have hurried the experience. However, I doubt that I could. Clarity and experience take time, and, if I got to where I want to be late, at least I got there. How many people can say that?

Read Full Post »

I had a call earlier this week from ABC News. With the trial of Hans Reiser for the alleged murder of his wife scheduled to start next week, the reporter wanted background on the free software community and how Reiser is regarded. Since I wrote an article last summer about Reiser’s struggle to get his work accepted into the Linux kernel, and another one shortly after his arrest about how his company was going to carry on without him, I’m the person from whom the mainstream media is looking for answers. In the past six months, I’ve been interviewed by The Oakland Tribune, The Wall Street Journal, and People on the same subject. And, each time, it leaves me with a deep sense of ambiguity.

For one thing, I’ve never actually met Reiser. I only exchanged a few emails while doing my earlier story, and fielded some complaints from him about what I said. For the second story, I also corresponded with his father. But these contacts were brief, and hardly make me an expert. I suspect I’m being called for background mainly because these articles pop up in a Web search, but I hardly feel qualified to give the comments for which I’m asked.

For another, so far as I’m concerned, these stories were only minor parts of my working life. I had some small pride in the first story for its thoroughness and attempts at balance, but neither the Linux kernel nor Reiser’s work on his filesystem are beats that I cover regularly. The second story is especially minor, an update that helped me fill my monthly quota of articles. When I consider the comprehensive articles I’ve done that have been largely ignored, I’m irked that the second one should be the part of my output to receive so much attention.

Most importantly, I have no wish to join the chorus of speculations about the case. In the second article, I made a conscious choice to focus on the technical issues because I thought that to do otherwise would be in poor taste. I don’t even care for mysteries unless they are a facade for a historical novel, so covering or discussing a real life murder is profoundly distasteful to me.

Nor, for the record, do I have any predictions about the outcome. From what I’ve seen and heard about Reiser, I would be no more surprised to hear him declared innocent than to hear him found guilty. I simply don’t know enough about him to form a meaningful opinion. Either way, the case seems like a tragedy for everyone involved – and that’s as far as I care to go.

All the same, I found myself replying to each request for comments in some detail, and I’m still not altogether sure why.

Part of the reason, I suppose, is the implied compliment. Online journalists may have more readers than colleagues in the mainstream media, but we’re not nearly as well-regarded. So, to an extent, I feel that the requests lend legitimacy to my daily work.

Even more importantly, I feel that, if I don’t give a reply, my mainstream colleagues will simply move on to someone with less knowledge of the free and open source software community and less of a sense of responsibility. Since I have a detailed perspective of the community, I honestly feel that I can express the range of reactions better than most people. Hans Reiser is a person whose work is both admired and pilloried, and whose personality often interfers with sober judgment of his accomplishments, and I can point out this range of opinions because, unlike many people, both my job and my temperment keeps me interested yet distanced from the various issues.

But, mainly, I’m simply too damned polite to refuse despite my own ambiguity. So, I talk, but, not so deep down, I keep feeling that being party to the coverage of the case at all is enormously gauche. In fact, there are times I wish I’d never written about Reiser at all. Had I known the consequences, probably I wouldn’t have.

Read Full Post »

« Newer Posts