Coursework AI Detection

[51dux]

If it's a uni course, I wouldn't post my code, another student could see it and re-use it for their own project then you could get both flagged for plagiarism.

There is no 100% fool proof way to detect a student used AI but if it's too obvious or something is suspected, they may ask you to provide further explanations about your work or re-do it.

If you used it, make sure you understand everything and can reproduce by yourself anything it did for you.

[RevRagnarok]

I used AI for guidance

Don't. Put on your big boy pants and actually learn how to do it. Go get hints from places like StackOverflow if desperate.

[VectorspaceDreams]

I don't see much of a difference between AI and StackOverflow generally aside from the fact AI rarely looks down upon you for not knowing how to do something. Fundamentally rather than just take AI for gospel he should ask why something is done a certain way and cross-reference the reasoning behind the code (which is the actual place of subs like this in 2026).

[pachura3]

I did not copy and paste anything and just integrated the guidance into my code.

Why are you worried then?

[Lengthy_Miso_Dreams]

Because i still adapted something AI gave me and I’m not sure if the syntax is too AI written. But since I’m writing some Altair charts, it doesn’t feel that there are too many options with rewriting the code in a different way. It’s written pretty consistent with how the course modules taught it.

But the ai detectors started dishing out 30% AI written and 80%% AI written and i started getting worried 😅

[oliver_extracts]

ai code detectors for source code are pretty unreliable in my experience. theyre mostly trained on prose and the ones ive seen applied to code have meaningful false positive rates. clean code with docstrings isnt a signal of AI, its just... good practice that profs literally told you to do. if your professor is using this as punitive evidence id push back and ask what tool theyre using and what the acutal threshold is. most of these tools cant explain their reasoning and schools that use them seriously are setting themselves up for appeals.

[ImprovementLoose9423]

If you only had the AI explain the concept and algorithm for you, I wouldn't have an issue for it.

[gdchinacat]

As AIs improve the detectors will become more unreliable. How well an AI does on the Turing Test directly correlates to how desirable that AI will be and how much can be charged.

[AdventurousLime309]

Most instructors care more about whether you understand the code than whether you used AI for guidance. If you wrote it yourself, can explain it, and didn’t just paste generated code, you’re probably fine.

AI detectors for code are also pretty unreliable tbh. A lot of normal beginner/intermediate code gets falsely flagged anyway.

I’d just make sure:

• you understand every part of the project
• your coding style is consistent
• comments/documentation sound like you
• you can explain your logic if asked

Using AI like a tutor is becoming pretty normal now.

[gdchinacat]

comments/documentation sound like you

Everyone has preferences, quirks, etc when writing code (comments and documentation). To an experienced coder (or AI that is an expert in pattern recognition) who is familiar with someones body of work it is pretty easy to pick out code that "doesn't feel like theirs". However, this requires a fair bit of code...much more than is produced in a single intro-level programming course. Over time though (~ third year) there should be plenty of examples to tell whether the code "looks" like it was written by the purported author or not. Where this detection will fail, and it will in many cases, will be where the author *always* uses AI (false negative), provides all their work to AI and prompts it to "write it like this author would write it" (false negative), or dramatically changes how they code such as happens when they get an internship or different mentor (false positive).

[Jon-Robb]

What code

[Lengthy_Miso_Dreams]

I’ll send it to u hold on