How do individual contributors get stuck?

Mar 9, 2017 | Newsletter

Subscribe to Engineering Impact, the weekly newsletter for managers of software teams.


 

This week: Why developers get stuck, how not to be a seagull, the bottom 20% of developers, small code is better code.

 

an effective strategy to get developers to work in their strength zones and side-step their weaknesses

LEADERSHIP

How Do Individual Contributors Get Stuck?

Noticing how people get stuck is an effective strategy to help people work in their strength zones and side-step their weaknesses. Camille Fournier breaks down some ways that contributors get sidetracked or stuck, so you can help.

Read the full post→

 

why software engineering managers need to understand the weight of their title

CULTURE

Don’t Be a Seagull

The anonymous manager writing over at retrospective.co describes the problem with ‘seagull management’ and understanding the weight carried by your title.

 

A discussion on what the bottom 20% developers are doing

COUNTERPOINT

Who are the bottom 20% of programmers?

Everyone talks about 20%, 5%, 1% or 0.1% developers and how to become one. Responders to this Quora discussion speculate on what these bottom developers are up to. Some interesting responses include this onethis one, and this one.

 

Or jump in and read the full Quora thread→

 

the real story of quality code

CODING

Smaller code, better code

Aaron W Hsu on the evolution on his compiler and the 750 Lines of Code that remain after 6 years of working on it: “In that time I’ve added roughly 4,062,847 lines of code to the codebase, and deleted roughly 3,753,677 line of code. And there’s the real story.”

 

 


If you enjoy Engineering Impact, sign up to get it weekly.

Ben Thompson

Ben Thompson

Ben Thompson is a co-founder at GitPrime where he leads design and customer experience. He is a Y Combinator alumni, with a background in product design, branding, and UX design. Follow @thebent on Twitter.

Get Engineering Impact: the weekly newsletter for managers of software teams

Keep current with trends in engineering leadership, productivity, culture, and scaling development teams.

how to use data to lead a successful software teams

A Data Driven Approach To Leading Software Teams

Learn how engineering leaders are using data to help their team increase productivity and become even more effective. We've analyzed over 40 Million commits to help you understand the important questions every software engineering manager needs to know.

Success! Please check your email for your download. You might also be interested in Engineering Impact: the Weekly Newsletter for Managers of Software Teams. Keep current with trends in engineering leadership, productivity, culture and scaling development teams.

Share This