00:56 - Chris’ Superpower: Not Knowing In Public
- Asking Questions
02:53 - Source Documents and Their Relation To People
- Grace Hopper
- Maintaining Code to Give People Context (Writing Code For People)
- Critical Complexity
- Indu Alagarsamy
06:44 - Encouraging Others To Write Code For People
- Modeling Behavior
- Event Storming
- ECO Mapping (Ego, Command, Outcome)
- Creating Culture
- Arlo Belshee: Naming is a Process
12:39 - Naming Things in Code / Narratives in Software and Business
18:53 - Asking the Right Questions
- Mobbing Interviews
22:38 - Interviewing for the Benefit of the Interviewee
- The Problem with Being Transactional
- It’s People All The Way Down
- Empathetic Interviewing
33:44 - Treating People as People; Making Things More Humane
- Books by Gerald Weinburg
- The Mythical Man-Month
- The Cathedral & the Bazaar: Musings On Linux And Open Source By An Accidental Revolutionary
- Willem Larsen
38:23 - Code Stores Emotion
- Measuring Progression
- The Valley of Despair
45:19 - Deciding: “Will this be helpful for someone else?”
Jessica: The idea that code can convey emotions. Even code can be Greater Than Code.
John: Structuring interviews with goals around comfort and familiarity so people can perform at their best.
Jamey: Imbuing things with the feeling when you wrote it.
Chris: If you’re feeling frustrated, kind is great. Also, everything is a systemic whole.
To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps. You will also get an invitation to our Slack community this way as well.
Amazon links may be affiliate links, which means you’re supporting the show when you purchase our recommendations. Thanks!Support Greater Than Code