You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My obsessive tendencies come out when I do creative work, and this has lead to the massive show notes section on each podcast episode. To be clear: I love doing the shownotes and they will continue to be a source of comedy and edification, but I need rules to limit/focus the content more and cut down on drafting time.
I will think about these rules in more depth later, but this issue is for reifying the fifth member of our podcast team: Jenevieves. Or the Four-Point-Fifth, if you prefer.
To get these off my mind:
If an 18-year old with an interest in technology would know the company name, then linking to their website is prohibited. Example: Amazon, Microsoft
If the topic is a common vocabulary like a sport like football, it's not necessary. Specific concepts from those sports are allowed. Like a touchdown from football.
If the topic is the topic of the segment, then it is always allowed. If we're talking about Amazon, I link to Amazon regardless of other rules.
The text was updated successfully, but these errors were encountered:
Do name the author of the article being discussed directly. Perhaps also major works discussed within. Authors of books? Directors of films? Just not the numerous random articles that illustrate points we talk about.
My obsessive tendencies come out when I do creative work, and this has lead to the massive show notes section on each podcast episode. To be clear: I love doing the shownotes and they will continue to be a source of comedy and edification, but I need rules to limit/focus the content more and cut down on drafting time.
I will think about these rules in more depth later, but this issue is for reifying the fifth member of our podcast team: Jenevieves. Or the Four-Point-Fifth, if you prefer.
To get these off my mind:
The text was updated successfully, but these errors were encountered: