For further actions, you may consider blocking this person and/or reporting abuse
18 Useful Github Repositories Every Developer Should Bookmark
18 Useful GitHub repositories every developer should bookmark: everything from learning resources and roadmaps to best practices, system designs, and tools.
Read next

Discussion: Is SQL Server still the best database for .NET Developers?
Miguel Teheran -

Difference Between Error and Exception With Examples
Fahim Zada -

chalk equivalent in Flask
Abel Lifaefi Mbula -

What keeps ya coming back to DEV?
Michael Tharrington (he/him) -
Top comments (3)
I try to apply Quantified Task Management, which I specifically designed for this purpose. Code is incredibly subjective, but I believe tasks can be boiled down to four measurements:
If you compare the averages of these measures, for all tasks a developer has completed in a given time frame, it gives a pretty good picture...
...now, in practice, I don't really apply this as much as I should. Shame on me. :\
While I heard the first time about this practice and think it's interesting, I wonder how help you give to coworkers will get into account.
In practice I find myself often helping other developers out, answering their questions and peer work with them.
That's a good point, and I haven't thought about it. I think it usually doesn't factor in too much, as only one person (two in pair programming) is going to actually be doing the coding. Anyway, if someone spends all their time helping everyone else to the exclusion of their own work, that's a problem. In a team dynamic where help is mutual, it should all even out.
That said, perhaps as a metric, half of the points could be granted to someone who helps significantly? It's definitely harder to measure.