How to Make Your Developers Unproductive and Unhappy Logo

Max Kanat-Alexander

Principal Staff Software Engineer

LinkedIn

How to Make Your Developers Unproductive and Unhappy

Summit Producer's Highlight

Max’s keynote humorously explores developer unproductivity, before describing some more serious DPE strategies like internal surveys, diverse team tooling, and flexible standards. His 20 years of insights may provide clues to finding your own successful path to DPE excellence.

Summit Producer's Highlight

Watch Video

About the session

Max’s keynote humorously explores developer unproductivity, before describing some more serious DPE strategies like internal surveys, diverse team tooling, and flexible standards. His 20 years of insights may provide clues to finding your own successful path to DPE excellence.

Watch the video Play Button

View the slides Arrow Down

About this talk

When you first start off with an engineering team at a small company, everybody is in the same room, and you can just ask developers what their problems are. As a company grows, it becomes harder and harder to be sure you’re building the right infrastructure for your developers. Eventually, understanding the problems to solve and prioritizing them appropriately becomes the most important part of successfully improving developer productivity.

In this talk, I will go over what we have done at LinkedIn to understand our developers, how we go about defining metrics and feedback systems for them, and what we have done to make that data actionable for our tool and infrastructure owners.

About this talk

Watch The Video

Get more DPE

The slides

Array
LinkedIn

Who is Max Kanat-Alexander?

Max is the Tech Lead of LinkedIn’s Knowledge Systems team, which helps engineers and engineering managers understand what they need to understand in order to do the best work they possibly can. He is the author of _Code Simplicity_ and _Understanding Software_.