whybother Labs · Developers
Adoption impact
Your team is producing more code. We built the dashboard around the metric that moved.
Adoption cohort. Weekly totals, compared with rollout. One maintainer throughout.
Lines written: up 30%. Things shipped: same. Reviewer: tired.
Lines written / week
Things shipped / week
PRs awaiting review / day
Reviewer
The adoption cohort
Generated code is counted on arrival. Shipped work is counted after review. These events are increasingly far apart.
| Period | Lines / week | Shipped / week | PRs / day | Review hours / day |
|---|---|---|---|---|
| Rollout | 10,000 | 3 | 1 | 0.5 |
| Week 1 | 11,000 | 3 | 8 | 1.5 |
| Week 2 | 11,800 | 3 | 16 | 3.0 |
| Week 3 | 12,400 | 3 | 28 | 5.0 |
| Week 4 | 13,000 | 3 | 40 | 7.0 |
The new contribution standard
Every generated PR includes a structured explanation. The maintainer can read it before reading the explanation of the explanation.
### 📝 Summary
Improves the empty state discovered during the fix.
### 🔧 Changes
Adds an empty state for the empty state.
### 🧪 Testing
Confirmed the PR description renders correctly.
### 🚀 Delivery
Ready for the maintainer's final implementation.
Closes: nothing.Required fields: all four headings. Acceptance criteria: supplied by the reviewer.
Complete the delivery pipeline
Generation is included. Reading every diff is available as a separate engagement.
Billed for the time spent understanding the change. Includes asking why the settings page needed another one.