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 1 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
3 sources. These accounts focus on private deployment, model governance, license protection, cost control, and what changes when Tabnine moves from one engineer to an organization.
Individual builders
44 sources. These accounts focus on completion quality, resource use, chat and model choice, and how Tabnine compares with the other assistants each developer runs.
All practitioners
47 sources. This gives the broadest read, but combines work settings and product eras that can reach materially different conclusions.
47 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual practitionerSolo developers and independent builders44 sources, counted here
Emphasizes Completion quality, resource use, and price
- Very small team2 to 10 engineers3 sources, counted here
Emphasizes Company approval, enterprise sign-in, and shared commands
- Professional team11 to 50 engineers, or a named company's teamNo sources from this setting yet
- Technical leadershipLeaders setting adoption across teamsNo sources from this setting yet
- Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet
What changes with scale. Individual developers judge Tabnine on whether the plugin works in their IDE, on completion and chat quality, and on what happened to their paid plan. The three team accounts turn to Enterprise sign-in, a purchase that did not hold up on a large codebase, and shared commands, which is where Tabnine now sells.