First thing you must self-measure is "Bugs per {feature|bug fix}".
Does fixing a bug introduced another bug or worst several bug? Same for features.
Having this metric result is not done in real time because you have to wait for QA or real users to report them. But have a list in a spreadsheet of the tasks you have completed with the name in one column and 2 other columns one for "End user reported bug count" and other for "QA or self-test reported bugs"
With this you will know the negative impact of your work and if the numbers are high you should be doing something about it like writing specifications first or making sure you're solving the right problem.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Don't measure lines of code period.
First thing you must self-measure is "Bugs per {feature|bug fix}".
Does fixing a bug introduced another bug or worst several bug? Same for features.
Having this metric result is not done in real time because you have to wait for QA or real users to report them. But have a list in a spreadsheet of the tasks you have completed with the name in one column and 2 other columns one for "End user reported bug count" and other for "QA or self-test reported bugs"
With this you will know the negative impact of your work and if the numbers are high you should be doing something about it like writing specifications first or making sure you're solving the right problem.