How Do You Know A Developer Is Doing A Good Job?

The text argues that developer evaluation is hard because the value of a single developer is difficult to measure directly. It says managers end up making subjective judgments, and that easy quantitative metrics often reward the wrong behavior.

It concludes that the best measures are qualitative, based on how a developer works with the team, solves problems, writes code, learns, and earns trust. Managers should communicate often and create a culture that rewards doing the right thing rather than looking productive.

Reading notes

#

• Developer evaluation is important for career, promotions, and raises, but the individual value that each person generates is difficult to measure.
• When the measure becomes vague, the criteria depend on the subjective judgment of managers, which can lead developers to try to sell themselves better instead of actually improving.
• Quantitative metrics seem attractive, but they can be gamed and end up changing incentives.
• Counting lines of code favors inefficient code, because good work may require less code.
• Counting branches or commits also distorts behavior, encouraging artificial fragmentation or small changes without real impact.
• Measuring bugs fixed can encourage superficial fixes and carelessness with deeper causes.
• The author argues that the best evaluations are qualitative, with a focus on being a good teammate, solving problems, writing good code, learning, and earning trust.
• For this, managers need to communicate frequently and create a culture that rewards what really helps the business.