10 years of driving developer productivity at Yelp | Kent Wills (Yelp)
Mar 26, 2024
auto_awesome
Kent Wills, Director of Engineering at Yelp, discusses the evolution of developer productivity efforts. Topics include forming the team, managing code ownership in a monolith, building a design system, standardization, LLM implementation, and demonstrating the value of their work.
Yelp focused on standardization while allowing innovation, transitioning from a monolithic structure to separate services.
Building a metrics platform and utilizing LLM tools enhanced support functions and streamlined service migrations at Yelp.
Deep dives
Origin of Developer Productivity Group at Yelp
The developer productivity group at Yelp started due to inspiration from Twitter's scaling methods where they aimed for standardization while allowing innovation. Initially focused on getting out of the monolith, they gradually built towards creating a design system team to manage common styles and components efficiently.
Balancing Standardization and Autonomy
Yelp's approach to standardization and autonomy involved collecting data and building a metrics platform based on engineering best practices. They navigated the challenge of enforcing standards by involving developers' insights and fostering collaboration. The team adopted a flexible yet opinionated stance, emphasizing centralization for efficient support and mutual understanding.
Evolution Towards Separate Services and Design System
Yelp transitioned from a monolithic structure by enhancing code ownership through team-based approaches before eventually moving towards separate services. The evolution of their design system, initially a style guide, highlighted the importance of consolidating common styles and components to facilitate scaling and maintain consistency across multiple front-end services.
Metrics Platform and LLM Implementation
Yelp's development of a metrics platform aimed at tracking key indicators like flaky tests and dependency updates provided insights for improving engineering practices. The introduction and ongoing evaluation of Language Model Learning (LLM) tools focused on enhancing support functions and streamlining service migrations by leveraging data-driven insights and automating repetitive tasks.
On this week's episode, Abi interviews Kent Wills, Director of Engineering Effectiveness at Yelp. He shares insights into the evolution of their developer productivity efforts over the past decade. From tackling challenges with their monolithic architecture to scaling productivity initiatives for over 1,300 developers. Kent also touches on his experience in building a business case for developer productivity.
Discussion points:
(1:42) Forming the developer productivity team
(3:25) Naming the team engineering effectiveness
(4:30) Getting leadership buy-in for focusing on this work
(7:54) Managing code ownership in Yelp’s monolith
(12:23) Supporting the design system
(16:00) The business case for forming a dedicated team
(19:45) How to standardize
(23:50) How their approach to standardization might be different in another company