AI for Measuring Developer Productivity

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-ai-coding-AI-and-developer-productivity-metrics-creators

1. Which approach aligns best with ethical AI-augmented developer productivity measurement?

   1. Monitoring keystrokes and screen time to gauge individual effort
   2. Using AI to automatically assign performance ratings to developers
   3. Focusing on team-level outcomes and surfacing workflow bottlenecks
   4. Tracking individual code commits per developer to identify low performers

2. What is a key reason to involve developers in designing productivity measurements?

   1. Developers will always approve of any measurement system
   2. Developers are the only ones who understand technical metrics
   3. It eliminates the need for manager oversight of the process
   4. Involvement ensures measurements align with actual work and builds trust

3. Why might measuring individual developer productivity through technical metrics lead to worse outcomes?

   1. Technical metrics are too accurate and expose all mistakes
   2. AI cannot actually measure any technical metric reliably
   3. Managers prefer not to have any productivity data
   4. Individual metrics create pressure that damages collaboration and trust

4. What role does transparency play in AI-augmented productivity measurement?

   1. Transparency is unnecessary because developers don't care about metrics
   2. Transparency helps maintain developer trust in the measurement system
   3. Transparency allows AI to measure more individual metrics accurately
   4. Transparency only matters for managers, not developers

5. When AI surfaces workflow friction in a development team, what should happen next?

   1. The team should ignore the data since AI is often wrong
   2. Developers should stop using the tools that show friction
   3. The team should investigate and address the underlying issues
   4. Managers should use it to identify individuals to punish

6. What is a fundamental limitation of using AI to measure individual developer productivity?

   1. Individual metrics are the most reliable way to improve team performance
   2. AI is not advanced enough to track any developer activity
   3. AI measurements are always more accurate than human judgment
   4. Individual productivity cannot be meaningfully captured by technical metrics alone

7. What does the lesson say about the relationship between measurement and developer trust?

   1. Trust is only affected by who sees the data, not what is measured
   2. There is an inherent trade-off that must be managed carefully
   3. Measurement always increases trust when implemented fairly
   4. AI eliminates the trade-off because it is neutral

8. Why should AI-augmented productivity measurement focus on team-level outcomes rather than individual metrics?

   1. Team outcomes encourage collaboration while individual metrics encourage competition
   2. Individual metrics have been proven to work in previous studies
   3. Individual metrics are too difficult for AI to calculate
   4. Teams are always larger than individuals, so metrics are more meaningful

9. What is an anti-surveillance principle in developer productivity measurement?

   1. Using AI to automatically fire developers who underperform
   2. Requiring developers to share all their code publicly
   3. Designing systems that avoid individual surveillance and protect trust
   4. Monitoring developers continuously to ensure they work efficiently

10. What type of outcomes should AI-augmented productivity measurement prioritize?

    1. The number of hours developers spend at their computers
    2. Meaningful outcomes that reflect actual team success
    3. Individual lines of code written per day
    4. How quickly developers respond to messages in chat

11. What happens when organizations use individual surveillance metrics to measure developer productivity?

    1. Productivity always increases due to greater accountability
    2. Trust is damaged, which can paradoxically reduce productivity
    3. AI systems become more accurate at measuring individual performance
    4. Developers become more collaborative and share more knowledge

12. How can AI help with developer productivity without crossing into surveillance?

    1. By surfacing patterns that indicate workflow problems across the team
    2. By automatically generating performance reports for HR
    3. By reporting individual developers who take too many breaks
    4. By tracking every action developers take in real-time

13. What is wrong with using lines of code as a primary productivity metric?

    1. Lines of code are the most reliable measure of developer ability
    2. AI cannot count lines of code reliably
    3. It encourages writing unnecessary code rather than solving problems
    4. It is too difficult to measure accurately

14. Why is it important to measure workflow friction rather than individual performance?

    1. Measuring individual performance is the only way to increase productivity
    2. Workflow friction identifies systemic barriers that affect everyone
    3. Friction measurements are required by law
    4. Individual performance is impossible to measure accurately

15. Which statement is most consistent with the material?

    1. Developer productivity measurement is fraught; AI helps surface meaningful signals while avoiding surveillance harm.
    2. Experts agree that no one should think about this issue.
    3. Every claim about this subject has been proven wrong.
    4. The topic has no bearing on day-to-day decisions.