Tech Blogging: In Defense Of Slowing Down
Two stories are currently attracting attention on Techmeme: rumors of a Digg sale, and some startup tips from Jason Calacanis. Both are rising on Techmeme in a rather amusing way, in which there’s a lesson about blogging in general: we may all benefit from slowing the heck down and not being in such a flurried rush to dash off a post and hit “publish.”
This morning, TechCrunch floated a rumor that Digg was about to be purchased by Microsoft or Google for around $200 million. As expected, tons of tech bloggers piled on with speculative posts. But a few hours later, Louis Gray Twittered a link to a post Digg’s blog itself from Jay Adelson – declaring the acquisition rumors completely false.
TechCrunch updated the original post with an “update” paragraph acknowledging Jay’s post, and claiming their source is “very, very good”. But there isn’t any way to shake the huge clot of blogs linking to the “Digg selling” story, and commenting on old – possibly untrue – news. This will all work itself off over time, but right now – I find it amusing.
Also today, Jason Calacanis posted 17 money-saving start-up tips. I thought most of the tips were decent and certainly had some useful insights (not buying a phone system and investing in dual monitors for example). But there was one tip about firing workaholics – that non-workaholics shouldn’t be in the startup “game” and would be better off working at Starbucks or the post office.
When I first read this, I figured Jason was just joking, but in his defense, there’s a kernel of truth to it. Passion and devotion at the expense of all else is one reason why I personally don’t currently work at one (too jaded after two startup implosions – I’ll take salary over stock options any day).
Anyhow, perhaps his post was dashed off without full thought as to the reaction of the tech blogosphere at large. Techcrunch in particular latched onto the negative implications – with the inflammatory headline “Calacanis Fires People Who Have A Life”, as well as others, with headlines I can’t really repeat here. Jason responded with a post explaining what he really meant, but those harsh words are out there already, in the form of the original post, now tops at Techmeme.
So at the end of the day, both examples demonstrate the worth of slowing down – resisting the urge to rush onto the “Techmeme pile up” or rattle off a blog post without re-reading it and just… pause a bit. Techmeme isn’t going anywhere, and your post will still show up when the time is right.