<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>engineering metrics on Kuldeep Pisda</title><link>https://kdpisda.in/tag/engineering-metrics/</link><description>Recent content in engineering metrics on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 14 Dec 2025 13:40:01 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/engineering-metrics/index.xml" rel="self" type="application/rss+xml"/><item><title>Developer Productivity Metrics That Don't Feel Like Surveillance</title><link>https://kdpisda.in/developer-productivity-metrics-that-dont-feel-like-surveillance/</link><pubDate>Sun, 14 Dec 2025 13:40:01 +0530</pubDate><guid>https://kdpisda.in/developer-productivity-metrics-that-dont-feel-like-surveillance/</guid><description>&lt;p&gt;Ever been asked that dreaded question: &amp;ldquo;How do we know the engineering team is being productive?&amp;rdquo; It sends a chill down your spine, doesn&amp;rsquo;t it? My mind immediately jumps to nightmares of stopwatches, keystroke counters, and managers celebrating the person who wrote the most lines of code.&lt;/p&gt;
&lt;p&gt;I once worked on a project where a developer was lionized for committing thousands of lines of code in a single week. We celebrated his &amp;ldquo;output.&amp;rdquo; The problem? We spent the next two weeks debugging the bloated, overly complex mess he&amp;rsquo;d created. That experience drove home a critical lesson: measuring the wrong thing is worse than measuring nothing at all. It&amp;rsquo;s like judging a novel by its word count instead of its plot.&lt;/p&gt;</description></item></channel></rss>