Histogram
The empirical density, binned linearly and clipped at the 99th percentile with an overflow bucket so tail outliers don't dominate the visual.
Abstract
For every engineer and every commit merged in the selected window, we compute the Engineering-Terminal-Value (ETV). This page replaces aggregate totals with three complementary statistical views of how that quantity distributes across each population.
Reading engineers and commits side-by-side separates a people story (output tracks individual capability) from a commits story (output tracks the size of merged changes) — see Figure 5.
The empirical density, binned linearly and clipped at the 99th percentile with an overflow bucket so tail outliers don't dominate the visual.
The cumulative share of total ETV produced by the bottom of the sorted population; is perfect equality, and the further sags below the diagonal, the more concentrated the distribution.
, with , is a scalar summary (0 = uniform contribution, 1 = all mass in a single entity); reported alongside the top-20 % share and the ratio as redundant sanity checks.
How Performance is spread across individual commits. Most commits are small; a few large ones carry disproportionate weight. The histogram uses a log x-axis because the distribution is heavy-tailed — on a linear axis everything collapses into the first bar.
Read each bar as: “there are this many commits whose ETV falls in this bucket.” Buckets are spaced logarithmically because the distribution is heavy-tailed — on a linear axis everything collapses into the leftmost bar.
feat(spanner): complete location-aware routing resilience and observability (#14418)
77aa4df · rahul2393 · Apr 14, 2026 · googleapis/google-cloud-go
Add comprehensive dependency injection support with IServiceCollection extension methods (#696)
58dadcb · Amir · Feb 25, 2026 · openai/openai-dotnet
feat: Add native Go 1.23 Iterator support (#3916)
91d01f7 · Mohamad Al-Zawahreh · Feb 2, 2026 · google/go-github
feat(workloadmanager): add new clients (#13849)
1328872 · shollyman · Feb 14, 2026 · googleapis/google-cloud-go
add gc support to Rust owned objects
75b49f9 · Yagiz Nizipli · Mar 18, 2026 · cloudflare/workerd
debt - fix some leaks found by copilot (#293731)
45a35b8 · Benjamin Pasero · Feb 9, 2026 · microsoft/vscode
RouteBuilder(s) unit tests
6d716c4 · Tracy Boehrer · Feb 9, 2026 · microsoft/Agents-for-net
chore: fix google3 import colabsqlviz tests (#2499)
3603b52 · Garrett Wu · Mar 10, 2026 · googleapis/google-cloud-python
Turbopack: Panic if a top-level task attempts an eventually consistent read (#89735)
89f3649 · Benjamin Woodruff · Feb 27, 2026 · vercel/next.js
[Workflows] Fix: implement workflows instance methods (#12881)
8729f3d · Olga Silva · Mar 19, 2026 · cloudflare/workers-sdk
Read a point (x, y) as: “the smallest x % of commits account for y % of the total ETV.” Diagonal = every commit contributes the same. The deeper the curve sags, the more a handful of large commits carry the window.
How Performance is spread across active engineers in the selected window. A flat histogram means the team contributes evenly; a long right tail means a few top engineers carry most of the output. The Lorenz curve bends toward the bottom-right in proportion to that concentration.
Read each bar as: “there are this many engineers whose total ETV in the selected window falls in this bucket.” Linear x-axis, clipped at p99 with an overflow bin on the far right so a couple of outliers don't dominate the view.
Read a point (x, y) as: “the bottom x % of engineers produced y % of the total ETV.” Dashed diagonal = perfect equality (every engineer ships the same). The further the curve sags below it, the more output is concentrated in the top few.
Is Performance a people story or a commits story? The same ETV, viewed two ways — once as how it piles up across engineers, once as how it piles up across individual commits.
Same Lorenz framing as Figures 2 and 4, overlaid. The x-axis is the bottom x % of whichever thing you're sorting (engineers for the teal curve, commits for the orange one); the y-axis is the share of total ETV they produce. Dashed diagonal = perfect equality. The deeper a curve sags, the more concentrated that dimension is.
Each dot is one of 643 engineers active in the selected window: x = commits shipped, y = average ETV per commit. Dashed lines mark the median on each axis, splitting the plot into four quadrants. Dot opacity and size encode total ETV — top performers stand out as larger, fully saturated orange. Read the chart by where the strongest dots cluster: upper-left = complexity specialists (few commits, each high-impact), lower-right = volume merchants (many small commits), upper-right = balanced stars, lower-left = peripheral.