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 Engineering leaders and teams.
Engineering leaders and teams
136 sources. Leaders' and teams' accounts cover why teams moved to Linear, how they hand issues to coding agents, what leaders miss when they report from it, and what made some teams go back.
Individual developers
162 sources. Developers' accounts follow daily speed, reliability, Jira trade-offs, and the ways they connect Linear to coding agents.
All practitioners
298 sources. Together these accounts give the broadest read. They mix teams that chose Linear with individual commenters, many of whom did not choose the tool they use at work.
298 sources from practitioners, by the context they work in. Filled rows count for this group.
- Individual practitionerIndividual developers and commenters, including those using Linear at work162 sources
Emphasizes Speed, reliability, and flexibility
- Very small team2 to 10 people or a small startup team100 sources, counted here
Emphasizes Agent handoff, planning views, and reporting gaps
- Professional team11 to 50 people, or a named company team15 sources, counted here
Emphasizes Sprints and reporting as headcount grows
- Technical leadershipLeaders deciding adoption across teams18 sources, counted here
Emphasizes Fit for product, design, and sales teams
- Organization-wideA rollout across a whole company or organization, by the source's own account3 sources, counted here
Emphasizes Planned or finished company-wide moves to Linear
What changes with scale. Individual developers focus on speed, sync, and agent handoff. Team and leader accounts, most of them from Reddit, praise the same speed and split on agent handoff and planning views. They raise reporting, time tracking, and cross-team views as the work Linear leaves to them.