chexxor
commented
5 years ago I think the (b), (c), and (d) audiences can all be satisfied at the same time at the cost of having a subset of the segments be boring. Essentially, each audience can be directly satisfied with one segment, and they can stick around for the other segments because "hanging out" amongst Pure FP fans and content is better than being bored.
I think (a) will also be satisfies by the just-mentioned plan, because they will learn the terminology, concerns, and culture of Pure FP fans, which can be hugely helpful to breaking into Pure FP languages.
The (e) audience will be the only audience we can't satisfy with this podcast, then, but only because the current podcast maintainers don't have expert skills in various aspects of the Pure FP field.
Great, so let's tag each segment with the audience it should target. This will be helpful when organizing and presenting content for these segments.
The audiences I've defined above aren't chiseled in stone, but they can be changed/redefined later. I'll add a wiki page or similar to track the audiences we'll target and define them.
An important parameter in deciding the kind of content to prepare for the podcast: Who is the audience of the podcast, and why are they listening?
(a) Know little about Pure FP and want to be educated about concrete aspects of it? (b) Basic, outsider knowledge of Pure FP and want to learn the culture with Pure FP fans? (c) Knowledge and experience of Pure FP and want to learn more concepts and practices? (d) Knowledge and experience of Pure FP and want to have fun with other similar-level Pure FP fans? (e) Expert Pure FP knowledge and want to discuss experimental or hypothetical Pure FP topics?
A constraint of defining the audience is what kind of content we are capable of sustainably producing in a long-term endeavor.
My capabilities give me confidence that I can do (b) or (c), but these are both relatively non-technical. I'm a bit worried about non-educational stuff, because I, personally, can't rate poorly an educational thing. On the other hand, I, personally, kind of like seeing the culture-sharing, "soft" side of software development in the podcasts I listen to.
However, I would quite like to have a bit of educational content, but my capabilities only allow me to educate on basic-level stuff. This would be quite boring for experienced devs, so we'd need to either recruit smarter people to help with those segments or find a way to make the boring content more interesting.