Around Learning
summary
Argues that the real bottleneck is learning not coding, claiming working code is a side effect so forcing predictability kills breakthrough experiments; shows the legacy-author “dungeon master” creates bus‑factor risk and that single person knowing everything is a big risk; recommends colocated sketching, pairing, deliberate offsite learning days and experimenting in high‑value domains; warns that learning is invisible so teams must measure and protect discovery, not only velocity.
AI-written summary · about
chapters (19)
- 0:00Intro
- 2:14WE NEED TO FEEL WE DID A GOOD JOB
- 7:53WHAT IS AGILE OPTIMISED FOR?
- 8:41HOW MANY DAYS IS A STORY POINT?
- 14:04LEARNING IS AN ASSET
- 23:00PO THINKS: "I AM GOING TO DO ALL THE LEARNING IN ORDER TO SPEED UP THE CODING"
- 26:34BUT WHO CAN TELL THE DIFFERENCE?
- 28:44WHAT'S THE LINK TO THE SPECIFICATION?
- 29:38SPECIFICATIONS ARE BORING
- 30:06I WON'T READ YOUR 200 PAGES SPEC
- 34:25LEARNING HOW TO RIDE A BIKE
- 36:42THERE'S A MISCONCEPTION ABOUT LEARNING
- 36:53LEARNING NEEDS MISTAKES
- 37:39EXPERT EXPERIENCE EXPERIMENTS
- 51:32REINVENTING THE WHEEL IS LEARNING
- 52:35REINVENTING THE WHEEL IS NECESSARY
- 54:32WITHOUT A REAL PURPOSE, WE'LL FIND ANOTHER ONE
- 57:45LEARNING IS GOING TO HAPPEN ANYWAY
- 58:06PURPOSE IS A GREAT DRIVER FOR DOING A GOD JOB
related talks
38mThe Myth of the Genius Programmer
42mGrowing a Learning Organization
47mKeynote: Out from under the Thumb of Silicon Valley
22mChoosing Failure
01h 00mThe Experimentation Mindset
45mMaking Learning Conscious — How and why to build a learning culture
52mKeynote: The Psychology of Code
30mLessons Learned: A Developer's Perspective on Teaching & Learning