193: Optimizing For Happiness with Tudor Gîrba
July 29th, 2020 · 1 hr 13 mins
About this Episode
02:09 - Tudor’s Superpower: Storytelling
- Getting Beyond Your Self-Critic
- Writing Code is Storytelling
- There’s No Semantics Without Syntax
13:04 - Reading Stories (and Code)
- Reading Code Takes Place in an Editor
- Code is Not Text. Code is Data.
17:56 - Optimizing For Happiness
- Automation Creates More Jobs
- Choosing Tools is Important
“The tools that we create end up influencing how we see the world.” – Marshall McLuhan
27:48 - Moldable Development
- Making Metaphors and Building Abstractions
- Glamorous Toolkit
32:50 - Editing Code as a Joint Activity
- rust-analyzer
- Simultaneous Perspectives Increase Communication Bandwidth
38:40 - Encouraging and Supporting the Presentation of New Ideas and Out-of-the-Box Thinking
58:41 - Culture is Formed by Storytelling; Identity is the Story We Tell About Ourselves
Reflections:
Rein: Reading and writing code can be different, but it can also be the same. See: the functional programming concept of lens.
Jessica: At the end of the presentation, if there’s no question that makes you think, then maybe you haven’t moved anything. Look for surprises.
Arty: Optimizing for happiness as a first principle. How do we do that more?
Tudor: With software, we are forcing people to listen to our ideas and then act according to our thoughts. That is a big responsibility, a privilege, and we have to train that skill.
This episode was brought to you by @therubyrep of DevReps, LLC. To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode
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.
Support Greater Than Code