Ask HN: Why is there a disproportionate amount of interesting text vs. spoken content?
I find it very easy, perhaps too easy to fill hours every day reading very interesting articles online. Then when I want to go outside for a walk, I would prefer to continue listening to similarly interesting content. I've found I take a lot longer walks if I'm engaged with an interesting podcast.
But there is a great divide here, it took a lot of digging just to find a few good podcasts (Stack Overflow, Venture Voice and Radio Lab), but they provide me less than 2 hours worth of content each week. With text, I wouldn't even be able to keep up with all the interesting content out there.
At this point I am fairly confident I have found most of the stuff I might be interested in listening to, so my interest now is to understand why more is not being produced, and if there is anything we could do to encourage production? Is there no demand for this? Are programmer types too shy? Why doesn't for example Steve Yegge just read aloud his blog posts and make them iTunes-subscribable?
13 comments
[ 3.2 ms ] story [ 42.1 ms ] thread* Many Internet users surf the web from their workplace or from public computers. Listening to audio in these settings, even with headphones on, is very difficult. This drives down the demand for audio. Heck, most people never even bother listening to audio when it is available, preferring to read through the transcripts instead.
* As a rule, anyone smart enough to be listening to programming podcasts can read faster than the podcaster can speak.
* Producing an engaging podcast takes more effort than writing an article. After all, you wouldn't want someone to just read out an article to you, would you? We expect more than just words from audio. A podcast would have to be scripted carefully to make sure it's engaging.
* Most geeks are excellent writers, but boring speakers.
* Text is searchable, audio (as of now) is not. How much metadata can you tack on to an audio clip, anyway?
* You can skim through text to see whether the content is worth reading or not. Skimming through audio is not that easy.
* Text allows more anonymity than audio.
It's not that people don't like podcasts. Audio is just too inconvenient a medium for most people.
Seems to me like audio content is added work that doesn't provide many benefits, at least for this sort of prepared content. Audio is more useful when recording spontaneous conversations.
Mostly, though, I think long walks (or better, bike rides!) are better for listening to what's going through my own head. I'm bombarded by enough information as it is. Other than that, "GeneralMaximus" sums things up nicely.
If you just want something other than reading there are quite a few video presentations available on Google Video (http://research.google.com/video.html). And naturally TED talks (http://www.ted.com/index.php).
I've written about how to run video in the background on an iPhone: http://blog.bumblebeelabs.com/running-videos-in-the-backgrou...
don't really do podcasts much myself, though. But these did keep me mildly entertained/informed a while back (esp. the HOPE conference about coupon hacking)
Of course, the easiest way to make a programming podcast both interesting and entertaining seems to be just to get Simon Peyton-Jones in it ;).
Hypertext: Random access, graph.
This has huge implications.
You might want to try the TWIT podcasts (http://twit.tv/). I'd call them easy-listening tech shows.