Developer Productivity

Stanford research in developer productivity has identified 0.1x engineers.

Code is an asset, but each line is a liability. Let’s explain.

By focusing on clarity, team composition, synergy, empowerment, and continuous improvement, leaders can build high-performance software teams.

No single metric can capture developer productivity and productivity doesn't revolve just around output.

Both activities offer similar rewards. Knowing that, how can developers easily learn new programming skills?

Have you ever wasted someone's time with a meeting without realizing? Or better still, have you ever wasted your own time with a meeting, only feeling that you've achieved something valuable, but actually circling back to square one? 

How to translate DORA metrics into tangible markers for measuring DevOps adoption and excellence? 

How do you determine whether to motivate your colleague towards progress or to respect their autonomy?

This article is a distraction. You should get back to your work! Or not? 

It seems that technical excellence is more satisfying for some developers than delivering customer value. This is where value streaming comes into play.

My three biggest productivity killers and how to fight them and my three productivity boosters and how to embrace them.

By understanding and leveraging these four metrics, Engineering Managers can make more informed decisions and lead their teams to higher performance levels.