The 4 Worst Software Metrics Agitating Developers in 2019
The worst KPIs to track a software team output: Lines of Code, Commit Count, Issues Resolved (aka “Shipping Velocity”) and Code Churn (aka "Efficiency").
- from
- Engineering Team Management
- added
- 2026-10-10
- likes
- 0
similar
-
The Most Important Performance Management Rule For Software Engineers staysaasy.com
“Merge code every week. That's what you should be saying to your new Software Engineering hire.”
-
Software Engineering's Greatest Hits youtube.com
When scientific method meet the practice of software development. My takeaways: the best metric is less lines of code, there is no 10x developers, too much unused configuration options, pair programing is for transfer of domain-specific knowledge and hackathon don't produce…
-
You're Not Managing a Team of Software Engineers, You're Managing a Team of Writers medium.com
Because writing software is “a creative process which is by its nature unpredictable and personal, in an environment which craves certainty, predictability and consistency.”
-
ast-metrics github.com
Static code analyzer for Go and other languages: complexity, coupling, cohesion and maintainability metrics, with HTML, JSON, Markdown and SARIF reports.
-
“Company I've worked for had manager who tried to ship features over the weekend with a ragtag team of developers who… news.ycombinator.com
Tactics of hustling managers, and how the company reacting to that kind of manager makes or break a good place to work.
-
CRO Metrics crometrics.com
Engineering Team Management › Key Performance Indicator (KPI): “The worst KPIs to track a software team output: Lines of Code, Commit Count, Issues Resolved (aka “Shipping Velocity”) and Code Churn (aka "Efficiency").”