Categories
Writing

The best of Verity Stobb

Last week I received two copies of the book, The Best of Verity Stob from Apress (ISBN number of 1-59059-442-8 for those Internet Explorer users that have AutoLink enabled). I was technical reviewer for the book, though in the end, I became more of language expert than a coding one, pointing out which of the British terms in the book could cause confusion for American readers. Half-way through I suggested a “Glossary of British Terms”, and am so glad I did, because it is absolutely hilarious–as is the rest of the book, which is geek humor at its best.

If you don’t know Verity Stob, you learn much when you read the section in the book, About the Author:

 

Verity Stob has been a programmer for 20 long yeaers, and has extensive experience in many disciplines of the profession. Programming languages known in-depth include C++, Delphi, Visual Basic, plus scripting languages such as JavaScript, PHP, and–in a real crises–Perl. Can bluff her way in C# and Java, but there again, who can’t, eh? Ditto UML, XML, HTML, and any other -MLs you care to lob at her. Except for ML, itself, of course. Mostly Windows, bit of Linux at a push, Mac no way. (I’ll bung in a few methodologies later, bulk it up a bit.) Although currently living and working in London, prepared to be flexible…Definitely a team player…Very many good hobbies…Sorry, who is this for again? When’s the interview? I tell you, I’m not going if they use those damn Microsoft quizzes.

The book features the best of the Verity Stob column from EXE, Dr. Dobb’s Journal, and The Register, and includes, among other gems, several poems dedicated to technology, such as the following, which is destined to become popular with webloggers far and wide:

The Lincolnshire Poacher

When I went out contracting
in rural Lincolnshire
I’d fix the locals’ websites
by bosky broad and mere;
I’d fix them on my laptop, boys,
but my mobile bills were dear.
Oh, ’tis my delight when the bandwidth’s right
and the signal strong and clear.

The cost of getting on the ‘Net
was bleeding my firm dry.
And then I met a geezer
who told me of Wifi.
He told me of war driving
and was I glad to hear!
For ’tis my delight when the bandwidth’s right
and the signal strong and clear.

I learned to spot an access point
by chalk marks on the ground.
It seems that open networks
are scattered all around,
Right here I can surf happily,
but I did not tell you where.
Oh, ’tis my delight when the bandwidth’s right
and the signal strong and clear.

Good luck to fellow poachers
who do the chalky prep,
Bad luck to secure standards
and the threat of rolling WEP,
Good luck to dozy sys admins
who don’t protect their gear–
Oh, ’tis my delight when the bandwidth’s right
and the signal strong and clear.

Then there was the Antarctica firm that was infected with Visual Basic:

I was standing, hands in pockets, with the pilot of the rescue helicopter as he looked around the burnt-out ruins of the dome, shaking his head in disbelief.

“There’s one thing I don’t understand about this, Ms. Stob. How come you didn’t get infected?”

“That’s easy to answer. The thing is, I know that it’s possible to build anything–even an operating system–just by dragging and dropping a few controls onto a form. No, it’s all right–”

The pilot had taken a pace back in alarm.

“It’s OK, I was just kidding. Now, hadn’t you better go and get ready for take off? If we stay here any longer, we’ll all freeze.”

“OK, Ms. Stob.”

As he walked away, still suspicious, I took my right hand out of my pocket and looked at it. It had grown into a hideous, misshapen claw. Useless for typing, but fine for grasping the mouse and clicking things…”

The book is a wired, whimsical delight; the writing a unique representation of that dry, sophisticated, barbed British wit that can only arise from a people that have lived, crammed onto a little bitty island for centuries. But to return to my glossary, my favorite definitions are those for blimey, fag, monkey-juice and, of course, marmite:

Marmite

A pungent slime made from a yeast. That this item does not occur in the text, apart from here, I regard as a failing on my part.

The reviews for the book have been very positive; among them is this from Andrew Orlowski. I picked this one out specifically, because Andrew is so near and dear to our little bloggy hearts.

An interesting fact about Verity Stob is that her face has been kept hidden after lo these many years of writing for several publications. This still remains true regardless of the book cover photo, shown below, at Bookpool–because that’s not the cover of the book I received. And no, as far as I know, the photos shown are _not_ Verity Stob.

Regardless of hidden faces and mystery pasts, the book is a good read, well worth breaking your piggy bank to buy.

Categories
Media Writing

Give onto Harvard that which is Harvard’s

According to the Wikipedia article on citizen journalism:

Citizen journalism usually involves empowering ordinary citizens — including traditionally marginalized members of society — to engage in activities that were previously the domain of professional reporters. “Doing citizen journalism right means crafting a crew of correspondents who are typically excluded from or misrepresented by local television news: low-income women, minorities and youth — the very demographic and lifestyle groups who have little access to the media and that advertisers don’t want,” says Robert Huesca, an associate professor of communication at Trinity University in San Antonio, Texas.

The phrase, Citizen journalism usually involves empowering ordinary citizens is, I think the key to this statement. I doubt there’s a one of the those in the forefront of the new citizen or ‘grassroots’ journalism efforts in weblogging that wouldn’t agree with this, and most likely enthusiastically. Yet it is the demographics shared among these supporters that casts doubt on the nature of our new journalistic corp. One only has to look at those representing weblogging at the Harvard conference on Blogging, Journalism, and Credibility to see the truth in this. Of those who have been weblogging for any appreciable time, most, if not all, are white, affluent, generally male, and usually middle-aged. In addition, all but two, as far as I can see, have been or are professional writers and/or journalists.

Additionally, rather than help to empower those who have little voice, the majority of these people of the new ‘citizen journalism’ tend to link to each other more frequently than they do the misrepresented among the rest of the weblogging population. A search of Jeff Jarvis’ weblog finds mention of David Weinberger 964 times, while a search of David’s site shows a mention of Jay Rosen 81 times, while a search of Jay Rosen’s site… well we could go one. Even with Dan Gillmor’s new weblog, which just started in January, I found seven references to Dave Winer.

This perpetuation of a specific norm among participants isn’t unusual, though. I remember from my own studies in sociology that we are most comfortable with those whom we share the greatest number of important characteristics, such as economic status, color, nationality, and religion. So it’s not surprising that white males from a similar socio-economic background read and hence link to those who are similar. When discussions about the imbalance of sex in regards to exposure is raised in weblogging, and the men say, “But this is an equal environment, and I don’t let sex impact on who I read and why”, this is probably very honest: the men don’t let sex impact on them. Consciously. But who better understands and knows how to write for the white, middle or upper class, intellectual mind than a member of the same group?

This understanding of the inherent pull of ‘like to like’ is really what forms the basis of affirmative action. It isn’t that we think everyone is an active bigot or racist or sexist; it’s that people tend to view those who share a sameness more comfortably over those who do not. In our professional or social lives, which can include weblogging (and that’s fascinating when you think about the virtual nature of this environment), comfort extends to more favorable impressions, and hence can influence hiring, linking, as well as other positive social actions. It takes an effort, an actual breaking away of natural preference, to cure this bias in our viewpoints. Even with increased exposure to the other sex or other races or religion, the tendency to ‘like’ remains.

Within professional journalism, editors and publishers are aware of the influence of ‘like to like’ and have made efforts to bring in at least token representatives of the underrepresented–for economic reasons if not for reasons of fair representation. For instance, if a journal on Linux has 97% male readership, while 20% of Linux users are women, and it wants to increase the number of readers, it wouldn’t be unusual for a publication in this position to seek out women and get their viewpoint on the issue; or even actively recruit more women in editorial or writing positions. Why? Because all things being equal, there could be more bang for the buck going after a ‘group’ of people, rather than the ragtag among those non-participants in the dominant group.

So it’s not surprising, though perhaps is ironic, to see that there is actually better representation of women and blacks and other racial minorities in the professional journalist circles than there is in the so-called ‘citizen journalistic’ ranks of weblogging, because there is no economic or social incentive for the citizen journalists to look outside of their ranks. At least, not at the moment.

An odd thing about all of this is that the practice of ‘like to like’ is so entrenched in business and journalism that it also forms part of the sphere of comfort even to those who are adversely impacted by the effect. For instance, women grow up to see primarily white, male journalists, politicians, and business and community leaders. Though some women may applaud seeing women in any of these roles, others may actually be made uncomfortable–it upsets what is known and what the women have reaffirmed about the role they perceive for themselves in their environment. Because of this, you’ll find women among those who speak out against affirmative action or acts such as the ERA. Or, since we’re discussing weblogging, who speak out against those who make an issue of the lack of representation of women in most weblogging and other like events.

(Based on this perception of role conflict, when women do appear as journalists, they tend to be co-anchors rather than lead anchors; and cover more social rather than political or economic events. However, as my favorite sports reporter and weather forecaster demonstrate — times, they are a changing.)

To return to the conference: ultimately, it is primarily a celebration of ‘like to like’ even though ostensibly it is bringing together ‘insiders’ and ‘outsiders’. However, this type of seemingly ‘open but not’ event isn’t unusual for Harvard; it is a bastion of ‘like to like’, as witness stories in the recent past of wealth influencing grades and admission, as well as claims of discrimination in hiring practices. I’ve always found Harvard to be mildly fascinating with its ability to get away with the most outrageous ‘good ole boy’ club practices, as demonstrated so beautifully with the current flap from a recent conference having to do with lack of women in the sciences and engineering. In this case, the President of Harvard told to be ‘provocative’, does make a mistake that could have negative reprecussions–not so much by encouraging the myth that women are inherently not as good with math and science, but by ignoring the many studies, which have proven this to be false. You are allowed bias at Harvard, but not public ignorance.

As for Blogging, Journalism, and Credibility, what comes out of the conference, this position paper that has been touted, will be heralded as an important document by some, of mild interest by others, and with indifference by the majority of webloggers. Why the latter, especially considering that it represents many who are dominant within this environment?

The reason, in my opinion, is because the conference is so specific as to audience that even those who support the status quo won’t be able to find a common point of reference. Though we may be comfortable with the dominance of white, affluent, males, we are less so with the sheer, rather overwhelming scope of dispassionate intellectualism inherent in the roster. There are, literally, too many 5+ percenters in the crowd. We can’t identify, except for perhaps feeling as if we’re being placed into an inferior position, i.e. “this here group of really smart people are going to tell all of us how we’re supposed to do things, and it pissed me off.”

Case in point: Zephyr Teachout has received much press about her recent writings on the (failed) Howard Dean campaign. I have no problem with what she wrote on her experiences and perceptions of what happened during the (failed) Dean campaign, because a) I wasn’t there, and b) it’s old news. However, I am interested in one statement she made in her FAQ:

I started this blog recently because of an upcoming conference on blogging, journalism, and credibility at Harvard’s Berkman Center. I wanted to write about my own experience, to illustrate some of the thornier issues that come up with conflicts of interest, consulting and blogging. My continued purpose is to engage in the broader debate about how to build a credible medium.

This is where I take issue with Zephyr: she comes into this environment via a political weblog originated during a political campaign–an exception, not the norm for this environment–with no prior exposure to weblogging before, or frankly after, and then she wants to tell us all how we should do what it is we do. Frankly, in my opinion–writing as one of the outsiders who really make up the majority of the webloggers, though we don’t know it yet and lord help the rest of you ‘insiders’ when we do–Zephyr doesn’t know blogging from beans.

If one were to extrapolate from Zephyr to the rest of the attendees, one could say the same about all of them: even the other webloggers, who are, perhaps, too caught up in the mystic of being the new ‘journalism’ to remember that rebels move against the flow, not with it.

On which note, I conclude this first, and last, post on Harvard’s Blogging, Journalism, and Credibility.

Archived, with comments, at the Wayback Machine

Categories
RDF Writing

2005 Errata and book updates: Chapter 1

I still like my analogy to the elephant and the blind men, in chapter 1. People still see RDF, and more generally, the Semantic Web (or my preferred, the lowercase semantic web), from different viewpoints, and with different expectations. That hasn’t changed, and by the nature of the beast, never will.

Good. Keeps life interesting.

The W3C RDF working group has issued new and revised versions of the RDF specifications. This doesn’t impact on Chapter 1 that much, but will in the other chapters, and where differences in the writing as compared to the specifications arise, I will make a note.

One change in the book is that any reference to the URI yasd.com has no relevance to anything actually existing. I dropped this domain when it was so badly overrun with email spam, it was no longer usable. As for the URLs in the chapter, those related to the specifications are:

RDF/XML Syntax Specification (revised)

RDF Vocabulary Description Language 1.0: RDF Schema

The RDF Primer

Resource Description Framework (RDF): Concepts and Abstract Syntax

RDF Semantics

RDF Test Cases

The graphic depicting the differences between RDF/XML and XML by Semaview no longer exists; sorry about that. However, I do believe my textual description does a decent job of explaining the difference. Comments, though, are welcome on this.

Page 8 references the ‘new’ ontology language work. Well, this group released specifications the same time as the final specifications were released for RDF, and can still be found here.

As for the rest of the chapter, most of the material in chapter 1 is more of a introduction for the rest of the book, so I’ll be updating the material as we come to it in the other chapters.

Categories
RDF Writing

Reviews and updated chapters

Recovered from the Wayback Machine.

I just read a review of Practical RDF out at Amazon that wasn’t very complimentary. In fact, I’ve had few complimentary reviews of the book, which can happen with a book. Sometimes you hit; sometimes you miss.

I can’t do much about the typos in the book (though these really were not as extensive as people say and have been corrected as errata at the book site at O’Reilly), because there won’t be a new edition of the book to make these corrections. I also can’t correct the style issues that have upset many of the readers, for the same reason – again, no new edition. But I can do something about new releases of technology that have happened since the book was first written.

I’ve already done so with the Java sections, but I think a better approach is for me to just go through each chapter at a time, and provide updated examples, new and updated information, and corrected links. I’ll then link these in the sidebar so that they’re easily accessible, and see if I can get O’Reilly to link to these chapter updates from the main book site. My hope is to have these updates done by end of January.

It’s not much, but it’s something I guess.

Categories
Writing

Technical writing and thankless tasks

I think that both Dana Blankenhorn and Marius Coomans will be good for open source, as they both question the concept without worry of offending the legions of open source fans, and seemingly without any axe to grind.

Dana recently questioned the lack of documentation and support associated with open source projects. In particular documentation, writing:

Documentation, I thought, is the Achilles Heel for open source.

It’s baked into the process. Great coders volunteer to write great code, but documentation is a go-to-market process, and when you’re giving stuff away that’s not part of the strategy.

His statement isn’t without merit; when you access many free, open source applications, the first thing you read is something to the effect that “this is free, so don’t expect support”. There’s some justification to this philosophy; it becomes a warning to users that the software they’re using is free; however, they’ll have to hunt around for support on their own, because there’s no one paying the bills for either documentation or support.

Marius agrees with Dana, but takes it a step further. In response to my push to have users be more responsive to those who provide both documentation and support for open source tools, he writes, in comments at his shared weblog:

Shelley, when was the last time you rang the phone company to thank them when you successfully placed a call? Documentation will never be appreciated because most of us only use it as a last alternative, when all else fails. Being a writer is a thankless job, so are garbagemen, car mechanics and loss adjusters. Live with it.

Ouch!

Having focused much of my time this last decade in technical writing, either for books or articles, tips, how-tos, and yes, documentation, I can agree with Marius, in that it seems to be a thankless task, at times. But there’s also something else implicit in his statement, whether it was intended or not: that it isn’t necessarily all writing that is thankless; it’s primarily technical writing that is thankless.

That leads me to wonder: is technical writing, or more specifically writing about technology, valued less than other writing? In other words, if we place the poet, the journalist, the writer of romance or the pundit on one scale, and the writer about technology on the other, will the scales tilt away from the technical writer, every time?