What sort of KPIs do you use on your engineering processes and infrastructure? Sprint Velocity, No of hotfixes, API response times, client bundle file size, etc, etc..
For further actions, you may consider blocking this person and/or reporting abuse
DEV Community
Timeless DEV post...
Git Concepts I Wish I Knew Years Ago
The most used technology by developers is not Javascript.
It's not Python or HTML.
It hardly even gets mentioned in interviews or listed as a pre-requisite for jobs.
I'm talking about Git and version control of course.
Read next
This Week In Python
Bas Steins -
How My Article Got Trended on Hackernoon But not on Dev.to
Elliot Brenya sarfo -
Meme... Tuesday? 🤔
Ben Halpern -
I Used ChatGPT to Answer Questions on Stack Overflow
Andrew Shearer -
Latest comments (2)
Just a random memory: after your metric becomes a targrt, it is no longer a good metric.
I'm always nervous about perverse incentives that can come out of measuring software engineering too closely.
Response times and bundle size seem reasonable, but I'm also not sure how you measure improvement apples-to-apples against theoretical alternatives there.
I've always worked with small teams, so engineering KPIs haven't always offered more good than bad. I can imagine in a larger org, it could help.
Now that we're open source I could see us working community PRs merged as a KPI. Seems to generally incentivize smaller PRs, more contributors, and feature/bug-fix velocity.