← Latest papers
💻 computer science

Academic Integrity and Emotional Responses to Inappropriate LLM Use in Software Engineering Education

This study surveys 116 undergraduate software engineering students to reveal that their emotional responses to perceived inappropriate LLM use are heterogeneous, ranging from indifference and guilt to relief and satisfaction depending on factors like learning risks, moral concerns, and deadline pressures.

Original authors: Ronnie de Souza Santos, Italo Santos, Giuseppe Destefanis, Cleyton Magalhaes, Mairieli Wessel

Published 2026-06-09
📖 5 min read🧠 Deep dive

Original authors: Ronnie de Souza Santos, Italo Santos, Giuseppe Destefanis, Cleyton Magalhaes, Mairieli Wessel

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 you are a student in a software engineering class. You have a massive coding assignment due tomorrow, you're exhausted, and the instructions are a bit fuzzy. You pull out your phone and ask an AI chatbot to write the code for you. You know, deep down, that the teacher probably didn't mean for you to do this. You hit "submit."

Now, the big question isn't just what you did, but how you felt about it afterward.

This paper is like a group therapy session for 116 software engineering students, where they were asked to confess their "AI sins" and describe their feelings immediately after. The researchers wanted to know: Do students feel terrible? Do they panic? Or do they just shrug it off?

Here is the breakdown of their findings, using some everyday metaphors.

1. The "Emotional Rollercoaster" Was Surprisingly Flat

You might expect that cheating (or using AI inappropriately) would feel like a rollercoaster of guilt, fear, and anxiety. But the study found something different. The ride was mostly flat.

  • The Most Common Feeling: The "Shrug"
    The most frequent emotion reported was indifference. About 36% of students felt nothing special. It was like eating a cookie you weren't supposed to eat; you knew you broke a rule, but you didn't feel a storm of guilt. Even when they knew they might get caught or that they weren't learning as much, they felt emotionally detached. It's as if the risk had become so normalized that it stopped feeling like a big deal.

  • The "Guilt" and "Anxiety" Group
    About 20% felt guilt, and another 18% felt anxiety.

    • Guilt was like a heavy backpack they had to carry. They felt they were cheating themselves out of learning, making them "weaker programmers."
    • Anxiety was like waiting for a bomb to go off. They were worried about the teacher catching them, failing the class, or getting kicked out of school.
    • Key Insight: These feelings were usually situational. They didn't feel guilty about the act itself as much as they worried about the consequences (getting caught) or the self-judgment (I'm not learning).
  • The "Relief" and "Satisfaction" Group
    Surprisingly, some students felt relief (18%) or even satisfaction (7%).

    • Relief was like finally taking off a pair of tight shoes. If the deadline was in one hour and the code wasn't working, using the AI felt like a life raft. The pressure vanished, and they felt good about surviving the storm, even if they knew it was a "cheat."
    • Satisfaction was rare but present. Some students felt like they were using a cool, futuristic tool to get ahead, viewing it as a smart move rather than a bad one.

2. The "Where" and "Why" Matters

The study looked at where this happened. It wasn't just one type of class.

  • The "Lost in the Woods" Phase: In early programming classes, students used AI because they were completely lost and didn't know where to start.
  • The "Writing a Novel" Phase: In classes requiring essays or reports, students used AI to write the text because they didn't care about the topic or couldn't organize their thoughts.
  • The "Tightrope Walk" Phase: In advanced classes or group projects, the pressure was high, and the problems were hard. Students used AI to fix bugs or finish group work because they were desperate to meet a deadline.

3. The "Rulebook" Was Often Blurry

A major theme was that the rules were often unclear.

  • Imagine a game where the referee says, "Don't use outside help," but doesn't explain if looking up a recipe counts as help.
  • Many students said the guidelines were vague. Some had never been told what was allowed; others were told "in general terms." This ambiguity made it easier for students to justify using the AI. They told themselves, "Well, the rules weren't clear, so I'm just being efficient."

4. The Big Takeaway: "Knowing vs. Feeling"

The most important discovery is a disconnect between knowing and feeling.

Usually, we think: If you know you did something wrong, you will feel bad.
This study says: Not necessarily.

Students could clearly see the risks: "I know I might fail," or "I know I won't learn how to code." But that knowledge didn't always translate into strong negative emotions. They could hold two thoughts in their heads at once:

  1. "This is risky and maybe wrong."
  2. "I feel fine about it because I had to get it done."

It's like driving 10 mph over the speed limit. You know it's technically illegal and dangerous, but if you're in a rush and the road is empty, you might not feel a single pang of fear. You just feel relieved you made it on time.

Summary

The paper concludes that for software engineering students, using AI inappropriately has become a normalized part of the routine. It's not usually a dramatic moral crisis filled with tears and panic. Instead, it's often a pragmatic decision made under pressure, followed by a shrug, a sigh of relief, or a quiet worry about getting caught. The emotional response is "muted," meaning the students aren't as emotionally invested in the "wrongness" of the act as we might expect.

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 →