• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Policy : Develop People Through Practice

Commitment to Learning Through Doing
We believe the best way to develop engineers is through meaningful, supported practice. Growth does not come from theory alone—it comes from building, debugging, collaborating, and stretching into new territory. Teams that learn together, grow together.

What This Means
We design day-to-day work so that learning is embedded, not incidental. Engineers develop skills through hands-on delivery, exposure to new domains, and peer-based learning. Mentorship, pairing, and reflection are part of the rhythm—not bolt-ons. Teams make space for growth and support each other in becoming better, together.

Our commitment to development through practice is built on:

  • Learning by Doing – Engineers grow through stretch assignments, role rotations, and reviewing real-world code. We use delivery as a vehicle for development.
  • Mentorship and Pairing – Mentoring, pairing, and mobbing are intentionally scheduled into team rhythms. Knowledge-sharing is active, relational, and embedded.
  • Shared On-Call with Support – Operational responsibilities like on-call are distributed equitably, with appropriate onboarding, training, and team support to build confidence.
  • Documentation as Learning – Docs are used to codify team knowledge and improve learning, not just to tick a compliance box. Writing and consuming documentation are active learning practices.
  • Cultivation of T-Shaped Skills – Teams deliberately build breadth across roles and domains. Developers learn about infra and CI/CD, platform engineers explore product needs, and data specialists understand delivery flow.

Why This Matters
If learning only happens outside of delivery, we create bottlenecks and burnout. Engineers feel stuck, growth is uneven, and critical knowledge gets siloed. When teams grow through practice, they become more adaptable, resilient, and engaged—and the organisation benefits from a stronger, more flexible engineering capability.

Our Expectation
All teams must embed learning into their delivery flow. This includes mentoring practices, pairing sessions, and creating safe opportunities for people to stretch into new areas. Leaders must model learning, provide feedback, and structure work to promote growth.

To support this policy, teams will be guided by development frameworks, pairing models, and playbooks for knowledge sharing. By developing people through practice, we build happier, stronger teams—and create a culture where growth is a shared, everyday pursuit.

Associated Standards

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering