Developers can accept, edit, or reject inline suggestions while build, review, and merge controls remain.
Collections: Human still decides
Executive brief
Real-world productivity evidence is more modest and noisier than lab claims; adoption and quality controls matter.
AI value · Pull requests completed per week
VerifiedAccess was associated with 7.51%-8.69% more pull requests per week, depending on specification.
Preliminary estimates were imprecise and statistically significant only under weighting for periods with stronger uptake differences.
Before
Writes implementation and test code manually. → Reviews submitted code and decides whether to merge.
After
Receives inline code suggestions and accepts, edits, or rejects them. → Reviews the complete human-owned change.
Human boundary
Developers decide whether suggestions enter a change; reviewers and repository controls decide merge.
Why it matters
Developers can accept, edit, or reject inline suggestions while build, review, and merge controls remain.
Before
How the work ran before the change.
Developer
Writes implementation and test code manually.
ControlTests and code review.
Reviewer
Reviews submitted code and decides whether to merge.
ControlStandard engineering governance.
What changed
Developers can accept, edit, or reject inline suggestions while build, review, and merge controls remain.
Decision rightHuman moves from creator to judge
After
How the same work runs now.
Developer with Copilot
Receives inline code suggestions and accepts, edits, or rejects them.
ControlDeveloper review, tests, scanning, and policy.
Reviewer
Reviews the complete human-owned change.
ControlUnchanged merge authority.
Exception path
Developers reject unsuitable output and code manually; failed tests or reviews block the change.
Decision authority
Developers decide whether suggestions enter a change; reviewers and repository controls decide merge.
| # | Actor | Action | Control |
|---|---|---|---|
| 01 | Developer | Writes implementation and test code manually. | Tests and code review. |
| 02 | Reviewer | Reviews submitted code and decides whether to merge. | Standard engineering governance. |
| # | Actor | Action | Control |
|---|---|---|---|
| 01 | Developer with Copilot | Receives inline code suggestions and accepts, edits, or rejects them. | Developer review, tests, scanning, and policy. |
| 02 | Reviewer | Reviews the complete human-owned change. | Unchanged merge authority. |
Work that left the path
Human role before
Developers authored code directly and reviewers governed merges.
Human role after
Developers supervise suggestions and remain accountable for code; reviewers retain merge control.
AI role
Decision mode: inline generation. Suggests code in context but cannot submit or merge.
Randomized Accenture developers without Copilot access.Access was associated with 7.51%-8.69% more pull requests per week, depending on specification.
Field experiment beginning July 2022. · 311 Accenture developers in the research sample.
Preliminary estimates were imprecise and statistically significant only under weighting for periods with stronger uptake differences.
Anti-pattern
Using pull-request count alone as proof of engineering value.
Questions
Portability conditions
Reputation risk
medium