Commentary

Thomas Claburn
 

Too Many Writers Spoil The Story

Blogger Jason Calcanis recently refused to be interviewed over the phone by Wired contributing editor Fred Vogelstein. Calcanis prefers e-mail. As Calcanis explained in an e-mail to Vogelstein, "I'm an email guy like dave winer.. And I own my words as well, and often print them on my blog (after stories come out)."

Blogger Jason Calcanis recently refused to be interviewed over the phone by Wired contributing editor Fred Vogelstein. Calcanis prefers e-mail.

As Calcanis explained in an e-mail to Vogelstein, "I'm an email guy like dave winer.. And I own my words as well, and often print them on my blog (after stories come out)."Calcanis's assertion of ownership poses a real problem for the sort of authorative writing practiced by publications like Wired, not to mention InformationWeek. The sources are seceding so they can speak for themselves. Everyone wants to direct.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The result is a conversation rather than a story. Imagine every film as Rashomon and you get an idea where this is headed.

This might be manageable if the narrators were better behaved. Then it really would be a conversation. Sadly, it's too often about ego.

Calcanis made that clear when, after telling Vogelstein he would need to adapt, he wrote, "Besides I have 10,000 people come to my blog every day--i don't need wired to talk to the tech industry."

Indeed, we can all speak for ourselves, on our own terms, in press releases. We can all behave like celebrities. Won't that be grand?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links