Fear in Tech
summary
Claims that culture drives technical outcomes: research shows psychological safety explains roughly 30% of team success, and managers overestimate visibility (88% vs 24% perceived). Concrete tools and rituals reduce fear: Kudos and monkey meetings make invisible work and mistakes visible; CI pre-merge tests, version control and monitoring create reliable predictions so changes are safe. Warnings are specific too: haunted legacy systems demand reconsecration, and LLMs act as a lossy compression of training data not a silver bullet.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 12:21Why fear matters
- 33:27Psychological safety
- 1:01:19Fear in systems
- 1:33:27Hype and measurement
- 2:01:13C++ future and growth
- 2:11:16Q&A
