For the past few years, every conference talk and vendor pitch has told us that AI coding assistants are going to transform software engineering. But what do the people actually using them think — not in a vendor-run demo, but six months into the grind of their real day jobs? This study tries to answer that with something rare in this space: actual longitudinal data.

The authors surveyed professional software engineers at two points six months apart, ending up with 158 responses in the first round, 101 in the second, and a matched cohort of 95 people who answered both times. That matched cohort is the gold here — it lets the researchers see how individual engineers' opinions changed as the honeymoon period wore off and the tools became part of routine work.

The headline finding from the abstract is that participants reported spending less time on most development tasks. That's the productivity story everyone expected. But the more interesting parts of a study like this are usually in the texture: how task focus shifts, how the experience of being a developer changes, and where the gains actually come from versus where they evaporate.

A few things make this paper worth paying attention to:

• It's a mixed-methods study, meaning the authors combined survey numbers with open-ended responses. That matters because "I'm 20% faster" and "I feel 20% faster but I'm rewriting more AI output than I'd like to admit" are very different claims, and only qualitative data catches the second one.
• It tracks the same people over time. Most existing studies on AI coding assistants are snapshots — and snapshots taken right after someone gets a shiny new tool tend to be wildly optimistic. Six months in, people have hit the walls: hallucinated APIs, subtle bugs in generated code, context-switching overhead from reviewing AI output, and the cognitive cost of trusting something that's usually-but-not-always right.
• It separates productivity from developer experience. These often move in opposite directions. You can ship more code while enjoying your job less, or vice versa. Treating them as one number hides the real story.

The key insight, even at the abstract level, is that the conversation has to move past "do AI assistants make developers faster?" That's a settled question for most tasks. The harder questions are: faster at what, at what cost to deep focus and learning, and whether the productivity gains persist or fade once novelty wears off and the harder edge cases dominate the work that's left.