Understanding Teams Through Systems Thinking and Stories
summary
Claims that teams improve when members share knowledge and practice systems thinking for toast not just tooling; shows concrete practices like blogging and using shared documents (OneNote/SharePoint) and a lived metric: ~60 million developers shaping 8 billion people. Demonstrates tools and failures: launches keysleft.com, rescues lost podcast files by inspecting FAT on an SD card, and debugs a Raspberry Pi bug caused by one byte (0x0D) removed by FTP ASCII mode, then publishes the episode.
AI-written summary · about
chapters (34)
- 0:00Introduction
- 1:26Welcome
- 3:03Attitude and Style
- 3:48Diversity and Inclusion
- 7:33Peepers
- 9:37Share your energy
- 10:41Conservation of keystrokes
- 11:15Where will you spend your time
- 11:41Working in a team
- 13:50Personal dynamics
- 14:51Years of experience
- 17:49Tim BernersLee
- 21:20Sponsorship
- 22:53Mentorship
- 23:33The Swiss Army Knife
- 24:22The Fundamentals
- 25:03Its okay to be a funny little knife
- 25:45Problem solving
- 26:38Systems thinking
- 29:35Early vs later
- 30:17Its always dns
- 32:38Collecting and remembering
- 33:37Layers
- 34:03Email example
- 35:28Name value pairs
- 35:50A simple example
- 36:33Altered Carbon
- 37:18Lost Files
- 39:07System Layers
- 39:46Collecting Patterns
- 39:57Debugging
- 40:10Weirdness
- 41:01File Transfer Protocol
- 41:21Carriage Return
related talks
59mKeynote - Building Teams Through Systems Thinking and Stories
46mEssentials for Building and Leading Highly Effective Development Teams
40mThe Art of Teams
49mBuilding Trust in Teams
11mLeading software teams with systems thinking
42mLeading Tech Teams in Uncertain Times
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
23mTrust Between Teams