Non-Violent Communication for Fun, Profit, and Self Defense
summary
Argues that Non‑Violent Communication (NVC) is a concrete toolkit for maintainer–user conflict, teaches the observations feelings needs requests (OFNR) pattern, uses the jackal and giraffe metaphor and the self‑check breath body need routine, cites Dunbar’s 150 as a limit that explains scale failure, recommends pairing practice and explicit requests versus demands, and reports that small practiced shifts reduce hostility and burnout while simple niceness often fails.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:25obligatory intro
- 0:50content warning
- 1:44software is social
- 2:04Conway's Law
- 2:45Dunbar's Number
- 5:09OSS Stereotypes
- 6:21Nonviolent COMMUNICATION A Language of Life
- 7:17Choosing Peace
- 9:003 parts of language
- 12:44OFNR - Warning
- 13:26Observation
- 14:41Feelings vs Thoughts
- 16:27Strategies
- 17:41Request vs Demand
- 19:41Tech Support 101
- 21:27OSS Team Management
- 23:48examples
- 27:30Process
- 29:03Jackal is not the enemy
- 29:50Practice
- 32:11giraffe voice
- 34:54giraffe ears
- 38:43burnout
- 40:38books
related talks
28mHow Non-violent Communication Can Help Keep the Peace on your Team
57mHow non-violent Communication can help keep the Peace on your Team
46mHow non-violent communication can help keep the peace on your team.
42mHow to Code in NVC Language - How to Decipher What We're Saying to Each Other
27mEmpathetic Pair Programming with Nonviolent Communication
40mClosing Keynote
56mFeeling Safe to be Uncomfortable
31mCare and Feeding of Open Source Developers: A Framework for Successful Communication