This chapter explores the challenges of gaining buy-in for initiatives, the importance of standardization in driving engineering effectiveness, and the delicate balance between standardization and developer autonomy. It discusses strategies for setting opinions and standards while allowing flexibility and discussion, emphasizing the need for centralization as a prerequisite for efficiency in large organizations.
Click here to listen to the episode transcript.
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
- (27:08) Demonstrating the value of their work
- (32:21) Building an insights platform
- (38:47) How Yelp is using LLM’s
Mentions and Links