Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 4 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
7 sources. These accounts focus on team rollout, automated review in CI, shared policy, usage cost, and what changes when Droid moves from one engineer to many.
Individual builders
78 sources. These accounts focus on model choice, planning, whether a session finishes, and how Droid compares with the other agents each builder runs.
All practitioners
85 sources. These accounts give the broadest read. They mix solo and team settings, which can reach different conclusions about Droid.
85 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual practitionerSolo developers and independent builders78 sources, counted here
Emphasizes Model choice, planning, and whether a session finishes
- Very small team2 to 10 engineers4 sources, counted here
Emphasizes Automated review in CI and several sessions at once
- Professional team11 to 50 engineers, or a named company's team2 sources, counted here
Emphasizes Merged work and cost per change
- Technical leadershipLeaders setting adoption across teams1 sources, counted here
Emphasizes Model policy and whether engineers keep using it
- Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet
What changes with scale. Individual builders judge Droid on model choice, on whether a session finishes, and on how fast the plan's limits run out. The seven multi-person accounts turn to automated review, parallel sessions, release stability, and how Droid compares with other agents.