← Latest papers
💻 computer science

Adapting homework design principles in modern Computer Science education to enhance learning outcomes and reduce unintended consequences

This study proposes and evaluates strategies for redesigning Computer Science homework to leverage, rather than prohibit, AI tools, demonstrating that iterative learning cycles, strategic timing, and continuous feedback can enhance genuine student understanding while maintaining academic integrity.

Original authors: Jamaladdin Hasanov

Published 2026-07-03
📖 5 min read🧠 Deep dive

Original authors: Jamaladdin Hasanov

Original paper licensed under CC BY 4.0 (https://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 Computer Science homework as a cooking class. In the old days, the teacher would say, "Go home, cook a lasagna, and bring it back tomorrow." The problem is, now there's a super-smart robot chef (AI) that can cook the perfect lasagna in seconds. If a student just asks the robot to make it and brings the dish to class, the teacher can't tell if the student actually knows how to cook or if they just bought a meal.

This paper, written by Jamaladdin Hasanov from ADA University, is like a new recipe book for teachers. It suggests three main ways to redesign homework so that students actually learn to cook, even with the robot chef in the kitchen.

Here are the three "recipes" the paper tested:

1. The "Live Stream" Cooking Show (Screen Recording)

Instead of just handing in the final lasagna, students must record a video of themselves cooking it, talking out loud as they go.

  • How it works: Students have to record their screen and their voice while they solve the problem. They have to explain why they are adding salt (or code) and show their hands (or mouse) moving. They can even show themselves looking up a recipe (searching Google or Stack Overflow) if they get stuck.
  • The Analogy: It's like a reality TV cooking show. You can't fake the process. If a student tries to pretend they cooked it by playing a video of someone else, the teacher can spot the fake because the "clock" on the screen won't match the time they claim to be working.
  • The Result: The paper found that this stopped students from cheating. It also helped them learn better because explaining the steps out loud (like the "Feynman Technique") forces them to really understand the recipe. Interestingly, when the teacher used an AI to grade these videos, the AI was a bit stricter than the human teacher, but it agreed with the human about who did well and who didn't.

2. The "Robot Taste-Test" (Critiquing AI)

Instead of banning the robot chef, the teacher says, "Okay, use the robot to make a lasagna, but then you have to critique it."

  • How it works: Students are asked to solve a problem, then ask the AI to solve the same problem. Their job isn't to copy the AI; it's to act like a food critic. They have to compare their dish to the robot's dish, find the mistakes the robot made, and explain why their way (or a different way) is better.
  • The Analogy: Imagine a student and a robot both build a Lego castle. The student's job is to walk around the robot's castle, point out where the bricks are loose, and explain why their own castle is sturdier. If the student just copies the robot, they fail because they can't explain the flaws.
  • The Result: This turns the AI from a cheat tool into a study partner. It forces students to think critically. The paper notes that while AI is good at making code, it often makes small mistakes in complex diagrams or logic, which students must catch.

3. The "Slow Cooker" Approach (Incremental Check-ins)

Instead of one big deadline at the end of the week, the homework is broken into tiny, daily steps.

  • How it works: Students must use a tool called GitHub (which is like a digital time machine for code) to save their work every day. They can't just upload the whole project on the last night. They have to show a history of small changes, like "I added the sauce today," "I fixed the crust tomorrow."
  • The Analogy: Think of it like a fitness tracker. You can't fake a month of running by uploading a photo of a marathon at the end of the month. The tracker shows your daily steps. If you didn't move for 29 days and then suddenly ran 26 miles in one night, the system knows you didn't actually train.
  • The Result: This stops "cramming" (doing everything the night before) and stops students from hiring someone else to do the work for them. It teaches them the real-world habit of working steadily, which is how professional software engineers actually work.

The Big Picture

The paper argues that we can't just ban AI or try to catch cheaters with stricter rules. Instead, we need to change the game.

  • Old Game: "Show me the final answer." (Easy to cheat with AI).
  • New Game: "Show me how you think, how you struggle, and how you judge the AI."

The study found that these methods make students more engaged, help them learn the material deeper, and make it much harder to fake their way through a class. It's about shifting the focus from the final product (the lasagna) to the process (the cooking).

What the paper does NOT say:

  • It does not claim these methods work for every single subject (like pure math or chemistry without computers).
  • It does not say AI grading is perfect; in fact, it showed AI grades were often lower than human grades.
  • It does not promise that these methods will fix all education problems, but they are a strong start for Computer Science classes.

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 →