It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
Some things are just qualitative. Metrics can tell you how much is being done in quantitative terms but it's never the full picture. Lines of code per hour is worthless; commits per day isn't much better; sprint velocity is heavily dependent on externalities (appropriate ticket scope, consistency, developer availability, difficulty of working with the codebase) so it really only works as a relative measure.
The only way to really assess productivity is to see if you can cash the checks you write: does this thing do what we want it to do, does it do it with reasonable efficiency and few bugs, did we get it done within the time we said we were going to get it done? If so, yay, we're adequately productive.
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.
Some things are just qualitative. Metrics can tell you how much is being done in quantitative terms but it's never the full picture. Lines of code per hour is worthless; commits per day isn't much better; sprint velocity is heavily dependent on externalities (appropriate ticket scope, consistency, developer availability, difficulty of working with the codebase) so it really only works as a relative measure.
The only way to really assess productivity is to see if you can cash the checks you write: does this thing do what we want it to do, does it do it with reasonable efficiency and few bugs, did we get it done within the time we said we were going to get it done? If so, yay, we're adequately productive.