Keynote: DevOps Lessons from a Primary School Teacher
summary
Classroom tactics map to concrete DevOps practices: claim that using zone of proximal development paces ramp-up (don’t leap from PHP to networking), the my turn our turn your turn sequence maps to driver/navigator to independent pair programming, and give one get one and talking chips (2–8 chips, ~2–3 minute turns) harvest and equalize knowledge in teams. Expert groups translate to enabling teams (Team Topologies) and asking high‑order questions with ~10 seconds silence deepens thinking. Also asserts that treating Postgres clusters as Kubernetes resources enables GitOps and Tekton pipelines for backups and PITR.
AI-written summary · about
chapters (10)
- 0:00Conference welcome
- 1:22Why focus on teaching
- 3:29Zone of proximal development
- 8:57Teaching strategies
- 11:50Knowledge sharing
- 12:53Team participation
- 15:19Expert groups
- 17:50Higher order questions
- 20:39Balancing question types
- 23:07Closing remarks
related talks
20mKeynote
26mKeynote Session: GitOps as an Evolution of Kubernetes
02mHighlights
17mKeynote: Nine lessons from Kubernetes in Enterprise
21mKeynote: In Search of the Kubernetes "Rails" Moment
06mKeynote: Beyond Automation: Kubernetes Success Requires a GitOps Mindset
20mKeynote
52mFrom Silos to DevOps to Platform Engineering: embracing GitOps and going behind the hype