[cstross]

This piece understates the problem, if anything. A lot of "journalism" today consists of regurgitating press releases rather than actually reporting on issues. And a lot of tech journalists have journalism qualifications but no tech -- gone are the pioneering days when the magazines found it easier to pick up techies and give them the basic training in journalism to communicate what they understood.

Consequently we find product reviews that are checklists of features, composed by writers who lack all insight or understanding of the subject. And outlets all-but-plagiarizing each others' regurgitated press releases.

(The disease isn't universal, of course. Some sources -- for example, anandtech.com -- get pretty close to the old-school hardcore reporting from time to time. Others actually cover industry movements from an informed perspective. But the drive to get eyeballs on ads is inimical to insight; it encourages facile, superficial, and above all speedy publication with a smattering of titillating headlines to draw the readers in. And it does us all a huge disservice.)

((Disclaimer: I spent years doing this for a living. I also have a CS degree, circa 1990 vintage. I may be viewing the old days through rose-tinted spectacles ... but I don't think so.))

[klint]

I'm a tech journalist -- I write for both TechCrunch and Wired Enterprise. I didn't write either of those pieces mentioned, but like many other tech journalists you'll find plenty of re-writes in my portfolio.

I'm speaking for myself and not from either company. But I can tell you though everyone in the industry is aware of the problem and trying to get away from re-writing to produce more original content.

The problem, as I see it, is that volume drives most online publishing. Making money depends on having updates throughout the day. That means every writer needs to post something every day -- usually more than one thing a day.

Even though most of these quick hit stories don't get many pageviews individually, they add up, and occassionally even a quicky will become a "blockbuster" that gets a huge number of pageviews. Original stories get a more consistently high number of hits, but they take much longer to produce.

I'm not sure people appreciate how much time it actually takes to write this stuff. Even doing quick hit journalism takes time. For example, I spent a couple hours this week on a post about Solr 4.0. It's short, and it's based entirely on the announcement/feature list but it still took a couple hours to write.

I have a bunch of original stuff I'm working on, but quick hit posts cut into the time I spend on those stories. At least part of that is a time management issue on my part -- and I'm a slower writer than many of my colleagues -- but I expect that juggling the needs to publish daily with longer form work is an issue for many tech bloggers.

(You should also not underestimate the amount of time we spend filtering information and looking for new -- e-mail, briefings, competitors sites, Twitter, etc.)

Anyway, I think things are slowly changing for the better thanks to reader demand for better content. But there's also a need to balance completeness of coverage with original work.

It's funny that Wired was singled out because I think they/we actually have a really good original content to re-write ratio (though yeah, Wired's always been known for sensationalist headlines). TechCrunch and Business Insider both have lots of original content as well. Because BI does so much volume I think people overlook the original stuff.

Another note about rosy retrospection: I don't want to defend the rewrite churn, but I do want to point out that even most daily newspapers have a significant amount of non-original content. Instead of re-writes though they tend to rely on newswires and syndicated columns and comics.

Re-writes aren't just done to get a quick post, they're also done to point readers to stuff they might not otherwise read -- as jbrodkin points out, not all TC readers read TorrentFreak. There are otherwise of getting this sort of stuff out -- like maybe just doing a linkblog that points directly to a story run elsewhere. In some cases it's possible to just call the original source and get the story so you don't have to link to/re-write a competitor's work -- I do this when I can but it slows things down (example: my story on Elbrus Technologies for Wired ran two days later than all our competitors because I waited for people from the company to get back to me instead of just basing my story on the EETimes report).

So yeah, it's getting better, everyone's worried about it but it's not simple to fix.

[nikcub]

While I was at TC there was a hard and fast rule that if a story had already been reported on another tech blog that we wouldn't write it, even if one of the writers was 90% done on his or her version of the story.

The only time this didn't happen was when there was a pre-brief and an embargo, which we usually got a head start on anyway.

Arrington was strict on this rule and that was his editorial style. If you talk to any writer from that time period ('06-'10) they would each have a half-dozen stories to share of stories they had been working on being stopped because somebody else published the same story first. It didn't even need an instruction from editors, it was just understood.

(this isn't a comment on the 'new' Techcrunch, I actually like it, the rewrite content doesn't get in the way of good original content from being written, and it usually adds new information to a story).

[MatthewPhillips]

So, what you're saying is that TC has the same people working on rewrites and features? Doesn't it make more sense to give the busy work to interns and let the higher paid journalists do original content?

[klint]

That's no differentiation -- there's just writers. I can't speak to why that's the case -- maybe because they don't want to make anyone be the person who does nothing but crap work. I don't think anyone sets out planning to do a bunch of rewrites anyway. In my experience it just sneaks up on you "Oh, well we should probably cover this and I need a post, guess I'll just do this real quick." That's just my experience, but there's certainly no one at TC telling me to do rewrites. I guess there's also varying definitions of what constitutes a re-write -- I don't actually always depend on a press release or anyone's else's coverage for every news short news story.

[jbrodkin]

When you cover a beat, a lot of times there are small stories that are worthy of a few paragraphs. But you often come across those stories while researching your beat and working on longer articles. So it often makes sense to divide up resources (the time of writers) based on topic rather than story length.

[nikcub]

I think you have a false nostalgia for what "old school" tech reporting was. Before web publishing and blogs, many tech magazines were nothing more than press releases and a couple of opinion pieces stapled together. It was trade press, not journalism.

Amongst the cabal of editors, PR and companies the racket was positive coverage in return for access.

At least today we have viable independent sources who can build an audience without giving a crap about access or offending PR people.

[mjn]

There was certainly a lot of trade press (PC World, many of the gaming magazines, etc.), but a number of the '80s and '90s tech magazines were pretty good, with independent content and reporting. For example: Byte, Dr. Dobbs, and the first 10 years of Wired come to mind.

[nikcub]

Byte, Dr. Dobbs, MSDN mag, Builder and the early Wired I remember fondly. Reading it really felt like you were part of something special, like a private audience with some of the smartest people in the world.

Those magazines were also hard to get, I would travel by bus to a larger library in the city, or download what was available via BBS. Everything that was mainstream such as the PC mags was just complete garbage. You were lucky to get 300 words in a tech section, and even then it would be something simple like teaching a DOS single command each issue.

For me that has been replaced by HN, reddit, other aggregators and a much broader range of sources. The difference now is that there is enough high quality content that I could spend 12 hours a day reading it, whereas 15 years ago I remember I would read all the magazines within a week or so and then eagerly wait out the following 3 weeks for the next issue to arrive.

There is so much high quality content on the web now. If there is any complaint, it should be that it is difficult to find and surface. I would love a pure technical, programmer oriented community that is not news related but rather just interesting advanced tech related, picking out old good stories from those good sources or finding real gems in individual blogs.

Most online communities and aggregators are too focused on content from the past 15 minutes. Even an article published 24 hours ago is seen as 'old news'.

[jbrodkin]

That's true. There was a time when it wasn't easy for regular folks to find press releases and announcements, so there were all these magazines marketed to IT pros and tech executives that just regurgitated marketing materials, and that could be perceived as being a valuable service.

Of course, some of the websites still do that :-) But you really need to add original reporting or analysis today to stand out.

[taylorbuley]

It doesn't really say the problem at all -- it just uses examples and lets the reader think between the lines.

They're great examples through. Exactly the kinds of reasons I got out of tech journalism.

[brudgers]

"A lot of "journalism" today consists of regurgitating press releases rather than actually reporting on issues."

E.g. most of what is written about Apple.