I've been working on a small tool that analyzes GitHub pull requests - not to measure speed or volume, but to find deep, high-quality contributions that often get missed in day-to-day reviews.
It’s especially useful at the skip-level, where some of the most impactful engineers can easily be overlooked.
Would love feedback if this is something that resonates with how you're thinking about team performance.
It's called Veritum: https://veritum.ai (free trial, no credit card), DM me if you need extra credits!
I thought the one universal truth that all devs agreed on was that using "metrics" or "KPIs" to score our work is a bad idea. This tool could be the greatest way of measuring dev work since sliced bread, it still would not be something I'd ever seriously consider using.
I've been working on a small tool that analyzes GitHub pull requests - not to measure speed or volume, but to find deep, high-quality contributions that often get missed in day-to-day reviews.
It’s especially useful at the skip-level, where some of the most impactful engineers can easily be overlooked.
Would love feedback if this is something that resonates with how you're thinking about team performance.
It's called Veritum: https://veritum.ai (free trial, no credit card), DM me if you need extra credits!
I thought the one universal truth that all devs agreed on was that using "metrics" or "KPIs" to score our work is a bad idea. This tool could be the greatest way of measuring dev work since sliced bread, it still would not be something I'd ever seriously consider using.
Fair, KPI for software engineering is shit distilled.