• Interviews spanned 12 software professionals across three sites at a large Swedish telecom, analyzed with process coding and thematic analysis, then interpreted through the extended Technology Acceptance Model (TAM2).
• The interviews surface a management-developer expectation gap that maps onto TAM2's constructs of subjective norm and voluntariness - how much pressure and choice developers feel around adoption.
• Participants weighed perceived risk heavily, a factor TAM2 and similar acceptance models don't represent at all, meaning standard adoption models may be missing a real driver of developer resistance.
• The paper's framing: AI-devtools are helpful but fallible assistants whose value is shaped by three factors together - organizational expectations, system scale, and developers' own skills - not the tool in isolation.

• context window — The maximum amount of text a model can consider at once — its working memory for the current conversation or task.

Offers a rare qualitative account of how developers perceive a company-wide AI coding tool mandate, useful context for anyone planning or managing a similar industrial rollout.

• articleThe Psychological Costs of Artificial Intelligence Adoption in Software EngineeringAdam Alami, Elda Paja, Abhishek Tiwari
• articleAI Policies: Help or Hindrance? A Software Developer's PerspectiveSamuel Ferino, Rashina Hoda, John Grundy, Christoph Treude, Hashini Gunatilake
• articleBuilding AI-Intensive Software with AI: Early Results and a Cautionary Tale on Measuring Development CostVictor Barros de Miranda Neves, Kiev Santos da Gama, Vinicius Cardoso Garcia

Checking sign-in…

Loading comments…