← Latest papers
🤖 AI

Taking a Pulse on How Generative AI is Reshaping the Software Engineering Research Landscape

This paper presents a large-scale survey of 457 software engineering researchers that characterizes the widespread yet uneven adoption of Generative AI in research activities, highlighting its concentration in writing tasks, the perceived productivity gains alongside concerns about trust and bias, and the urgent need for clearer governance and mitigation strategies.

Original authors: Bianca Trinkenreich, Fabio Calefato, Kelly Blincoe, Viggo Tellefsen Wivestad, Antonio Pedro Santos Alves, Júlia Condé Araújo, Marina Condé Araújo, Paolo Tell, Marcos Kalinowski, Thomas Zimmermann, Mar
Published 2026-04-14
📖 5 min read🧠 Deep dive

Original authors: Bianca Trinkenreich, Fabio Calefato, Kelly Blincoe, Viggo Tellefsen Wivestad, Antonio Pedro Santos Alves, Júlia Condé Araújo, Marina Condé Araújo, Paolo Tell, Marcos Kalinowski, Thomas Zimmermann, Margaret-Anne Storey

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine the world of Software Engineering research as a massive, bustling construction site. For decades, the architects and builders (the researchers) have been drawing blueprints, pouring concrete, and testing structures using their own hands and brains.

Now, a new, incredibly powerful, but sometimes hallucinating robot assistant has arrived on the site. This robot is Generative AI (GenAI). It can write blueprints, mix concrete, and even draft reports in seconds.

This paper is like a giant survey taken by the construction foremen to answer a simple question: "How is everyone actually using this robot, and are we building safe skyscrapers or just a pile of digital junk?"

Here is the breakdown of what they found, using some everyday analogies.

1. The Robot is Everywhere (But Not Everywhere)

The Finding: Almost 3 out of 4 researchers are using this robot. It's not a secret anymore; it's the new normal.

  • The Analogy: Imagine if 75% of chefs suddenly started using a "flavor-bot" to season their dishes. It's everywhere.
  • Where they use it: The researchers mostly use the robot for writing and editing. It's like using a spell-checker on steroids. They ask the robot to fix their grammar, summarize long articles, or brainstorm ideas.
  • Where they don't use it: They are very hesitant to let the robot do the heavy lifting of designing experiments or collecting data. It's like a chef letting the robot chop the vegetables (fine) but refusing to let the robot decide the recipe or taste the soup (too risky). They still want to be the "taste testers."

2. The "Pressure Cooker" Effect

The Finding: Many researchers feel pressured to use the robot, even if they aren't sure they should.

  • The Analogy: Imagine a classroom where the teacher says, "If you don't use this new calculator, you're falling behind." Even if the calculator is buggy, students feel they must use it to get an A or to look relevant.
  • The Reality: Researchers feel that if they don't mention AI in their grant proposals or papers, they might be ignored or lose funding. It's a "keep up or get left behind" situation.

3. The Trust Issue: "The Hallucinating Librarian"

The Finding: Researchers trust the robot for writing (77% trust it), but they barely trust it for designing studies (25% trust it).

  • The Analogy: Think of the robot as a very confident, fast-talking librarian.
    • If you ask it to "rewrite this paragraph to sound more professional," it does a great job. You trust it.
    • If you ask it to "find me a specific fact about 19th-century plumbing," it might confidently invent a fake pipe manufacturer. You don't trust it with facts.
  • The Risk: The biggest fear is that the robot will lie (hallucinate), steal ideas (plagiarism), or introduce bias without anyone noticing. It's like a librarian who confidently points you to a book that doesn't exist.

4. The "Human in the Loop" Rule

The Finding: To fix the trust issues, researchers say the robot must never be the final boss. A human must always check its work.

  • The Analogy: The robot is a junior intern. It can draft the report, but the Senior Manager (the human researcher) must read it, fact-check it, and sign off on it.
  • The Strategy: Researchers are adopting a "Human-in-the-Loop" approach. They use the robot to speed up the boring stuff (like formatting or summarizing), but they keep their hands on the wheel for the critical thinking parts.

5. The "Skill Erosion" Fear

The Finding: There is a worry that if young researchers rely too much on the robot, they might forget how to do the work themselves.

  • The Analogy: Imagine a generation of drivers who only use self-driving cars. If the car breaks down, they won't know how to steer, brake, or navigate.
  • The Concern: If students let the AI write their papers and analyze their data, they might never learn the deep skills of critical thinking and research design. The paper warns that we might end up with a generation of researchers who are great at prompting the AI but terrible at understanding the science.

6. The Call for Rules (The Traffic Lights)

The Finding: Almost everyone agrees we need rules, but they aren't sure what those rules should be yet.

  • The Analogy: The robot is a new type of vehicle on the road. We know we need traffic lights and speed limits, but we haven't decided yet: "Can it drive on the highway? Can it carry passengers? Do we need a license?"
  • The Consensus: Researchers want clear guidelines. They want to know: "Is it okay to use AI to write a review? Is it okay to use it to generate data?" They want to avoid a "Wild West" scenario where anything goes, leading to a flood of low-quality, fake research.

The Bottom Line

The paper concludes that Generative AI is a powerful tool, but it's not a magic wand.

  • Good: It speeds up writing, helps with brainstorming, and makes research accessible to non-native English speakers.
  • Bad: It can lie, it can make us lazy, and it can create a flood of low-quality papers.
  • The Solution: We need to treat it like a powerful assistant, not a replacement. We need to keep humans in charge, teach students how to use it wisely (not just how to prompt it), and build a set of traffic rules so the research community doesn't crash.

In short: Use the robot to sweep the floor, but don't let it design the house.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →