What does it mean to be code adjacent? Shawn Wang joins Henry to chat about not just open code but open thinking with his experience in community managing, the idea of tumbling, moderating /r/reactjs, starting the Svelete Society meetup, documenting and learning in public, being historians of our field, fresh notes vs. awesome lists, the meta language, and adoption curves. Transcript: https://maintainersanonymous.com/open-knowledge.

Shawn: https://twitter.com/swyx
Henry: https://twitter.com/left_pad

Headings:

Intro: Tumbling as an Alternative to Community Manager Specific, Limited-term Maintainer RolesSeparation of Maintainer ConcernsBabel W18, like YC W18Becoming a Moderator for /r/reactjsLearning with "I Promise to Answer Every Question"History and Memento Mori: A Time Before GitWhere's the Story of How Projects Get Started?A Culture of "Document Yourself More"Learning Gears: Explorer, Connector, MinerFinding A Vision People Can Rally AroundBeing Code AdjacentMaybe We Need a JavaScript Community ManagerCheat Sheets and Awesome ListsPersonalized Docs, Documentation LevelsOpen Source Knowledge, Proof of WorkTwitter as a Permanent Hallway TrackFind the Intersection of Two CommunitiesDocumenting Underlying Assumptions"Fresh notes"Starting a Meetup: Svelte SocietyKeeping it AliveTaking Part in Category CreationThe Meta LanguageParenting and Figuring Things OutNot Everything Needs to be in PublicCSS 4: Does It Even Matter if No One Knows?Adoption Curves: Focusing too much on the headRemoving the Learning Curve with Better DefaultsPhilosophy of TechnologySpatial Software, The Mind

★ Support this podcast ★

Twitter Mentions