3 ms·
For technical content, it looks like the burden of processing information was outsourced from people making content to people consuming content. Is it really sc
by jkukul 4y ago
For technical content, it looks like the burden of processing information was outsourced from people making content to people consuming content. Is it really scalable? Podcasting is one-to-many communication, so wouldn't it be more efficient if the 1 person who has something to say invested some time up-front to pre-process information to be more consumable for N people?
With all that said, I still listen to non-technical podcasts when I just want to get my mind occupied with random ramblings.
- ghaff 4y agoPodcasts work fine for a certain level of conceptual technical content. But the lack of visuals and the fact that the listener is probably doing something else at the same time limits how in-depth you can go. I've done interview format podcasts but, to be honest, I mostly don't listen to podcasts on technical topics myself.
- cxr 4y ago> Podcasting is one-to-many communication, so wouldn't it be more efficient if the 1 person who has something to say invested some time up-front to pre-process information to be more consumable for N people? Alternatively, a podcast where a fraction of its N listeners could do one thing each to contribute to how the thing is consumed for others scales even better (given a high enough threshold value for N). We've seen how beneficial rules of thumb like Wadsworth's constant can be, or how valuable it is to come across a comment that gives a timestamped table of contents/index for YouTube videos when the creator hasn't provided one themselves. A successful business built on taking that kind of intent and applying the wiki approach to it is probably inevitable.