Writing
Measuring engineering throughput without inventing metrics
2026-06-25
Recruiters are right to be skeptical of throughput claims. "10× engineer" language is meaningless. What helps is a repeatable measurement with explicit caveats.
The figure
This site cites ~2,951 GitHub contributions in the trailing year on the home page and in the about section methodology. The same figure appears in résumé lane A because it is approved for public use with the method below.
Method
- Pull GitHub profile contributions for the trailing 12 months (commits, PRs, reviews, issues as counted by GitHub).
- Record the measurement date and tooling version in the about page methodology section.
- Never mix contract delivery counts with open-source counts — they measure different things.
Caveats
- GitHub contributions are a proxy for sustained engineering activity, not business outcomes.
- Private repository work is excluded from public counts by design.
- Agent-assisted commits are included — the claim is about orchestrated delivery velocity, not manual typing speed.
If a metric cannot survive that level of scrutiny, it should not be on a senior portfolio.