What kind of developer are you, and what is your quality reputation? If we tracked programmers like baseball players, what would we see on your “programmer baseball card”? Let’s compare two developers side-by-side that way.
In contrast, we have Sam who at first glance does not seem to do as well as Joe in some areas. He’s written far less code, he’s missed more meetings, and he often doesn’t finish his sprint tasks on time. Sam does need to improve his estimating and his attendance, but we can see from his other stats that these delays come from Sam’s commitment to finishing his work and testing it well. He has far fewer bugs than Joe, fixes nearly all of them, and his bug fix rejection rate is practically zero. Moreover, Sam’s statistics improve each year. This is why he has a reputation for quality. In light of this, we can see the reason Sam writes fewer lines of code: it does not indicate low productivity; rather, he takes the time to get his code clean, right, and nicely factored.
Determine the quality reputation you want to have and let that drive your behavior.