📎 Webclip
Deliberate practice: The art of teaching and learning
The author says everyday work slowly builds knowledge, but it is hard to use that alone to close specific gaps. To speed up shared understanding, he introduced deliberate learning sessions built around focused exercises instead of presentations.
Reading notes#
- Knowledge about tools, code, and applications grows naturally through day-to-day work, but it takes time.
- Regular presentations, pair programming, and pull requests already shared knowledge, yet they did not reliably address specific gaps.
- The learning sessions were practical and focused on areas that needed attention, with everyone pushed a little outside their comfort zone.
- The exercises were small and playful, such as listing applications from memory, finding the cause of an outage, or drawing the components involved in one customer request.
- A challenge works because day-to-day work does not always feel like a learning opportunity, and deliberate sessions make it easier to stretch without the pressure of failure.
- Pairs are useful because two people can build on each other’s knowledge, while larger groups can leave the person who is most lost out of the discussion.
- Keeping exercises to about half an hour lowers the cost of participation and can make the time pressure feel more realistic.
- Repeating the sessions weekly leaves room to revisit topics and process what was learned.
- The format makes it easier to see what people struggle with, because they can say more clearly what feels unfamiliar and the team can notice patterns of missing knowledge.
- The author ends by comparing this approach to school, where short, focused, repeated sessions are the norm.
