Bring FP to Work
summary
Slides claim that technical demos alone fail: after 3 group meetings, 5 blackboard sessions and a proof of concept app adoption remains slow, so persuasion beats argumentation. The concrete strategy is empathy, active listening, leading from behind, building credibility by doing object‑oriented work with the team, celebrating small wins, and teaching immutability, Option/either patterns, separation of concerns and higher‑order functions first. Success measures are uptake over months, fewer runtime nulls, and a steady rise in contributors using the new patterns.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:26The Wind and the Sun
- 1:57Life is too short to be functional
- 4:19People
- 16:40Change is hard
- 17:58Progress
- 24:11Common Mistakes
- 25:08Avoid These Terms
- 28:10ObjectOriented Programming
- 33:07People Strategy
- 40:45Tech Strategy
related talks
43mBringing Functional Programming to Work
33mMaking the Leap from Execution to Strategy
51mEffecting Change—The Art of Leading Teams
42mHow Doing the Little Things Well Makes the Big Things Possible
45mPeople, Process, & Patterns
46mEssentials for Building and Leading Highly Effective Development Teams
01h 00mImproving Your Team(work)
18mAgile leadership and technical mastery, a harmonious alliance