Navigara
Google

adk-go — Engineering Performance

7 engineers all time · Jun 2025 – Aug 2026 · built 2026-08-23 · GitHub

Performance snapshot

Today's rolling 90-day reading for adk-go, compared with the start of the series. Pick a window to move that comparison point.

Eff. capacity added

−1.7engineers

3 devs deliver like 1 (0.4x pre-AI)

Avg. perf / dev / mo (ETV)

−66.8%

1.16 → 0.39

Active engineers

−40.0%

5.0 → 3.0

Features

−0.1pp

37.9% → 37.8%

adk-go vs. Google

Per-engineer ETV for adk-go against Google as a whole. Both lines are 90-day rolling averages scaled to a 30-day month, so they share one axis and can be read against each other at any point. Pick a window to zoom the chart to it.

adk-go
0.39ETV / dev / mo
0.62 (61.4%) past 90d
Google
2.05ETV / dev / mo
+0.66 (+47.5%) past 90d

Performance over time

ETV stacked by Features / Maintenance / Tests / Docs / Fixes — 90-day moving average, normalized to ETV / month.

Engineering capacity

Effective engineers behind adk-go, in pre-AI terms. Per-engineer ETV divided by the Q1 2025 baseline of 0.86 ETV / dev / mo gives a capacity multiple, and that multiple applied to the engineers active in the trailing 90 days turns it into engineer-equivalents. The line is the real headcount, so the gap between line and area is what the leverage is worth.

Effective engineers
1engineer-equivalents
−2 engineers above real headcount
Real engineers
3engineers
active in the trailing 90 days
Capacity vs pre-AI
0.4x
per engineer, vs 0.86 ETV / dev / mo

Knowledge concentration

How dependent is this repo on a small number of engineers? Higher top-1 share = higher key-person risk.

Top 1
21.6 %
Top 3
54.8 %
Top 5
79.5 %

Dmitry Pasiukevich owns 21.6 % of commits.

Reports

Written summary of the work completed each month.

No monthly reports available yet.

Most impactful commits

Top 10 by ETV in the all-time window.