AI-Generated Code Detection: The New Frontier in Academic Integrity
As AI coding assistants become ubiquitous, learn how institutions are adapting to detect AI-generated code and maintain educational standards.
Expert insights on AI code detection and academic integrity
As AI coding assistants become ubiquitous, learn how institutions are adapting to detect AI-generated code and maintain educational standards.
Stay ahead with expert analysis and practical guides
General
12 min
I kept every take-home submission from six bootcamp cohorts and ran them through three scoring passes. Here is what the numbers say about AI-generated code, which signals survive contact with real students, and where every detector I tried still gets it wrong.
General
13 min
Your CI already gates on tests, lint, and a dependency scan. AI-generated code walks straight through all three. Here's what a detector actually measures in a pull request diff, where the signal goes quiet, and how to wire the check into a merge gate that reviewers will tolerate.
General
4 min
Most teams think they have license compliance because Dependabot runs. They have a dependency list. A working gate needs three separate scans, and the third one catches the code that never appears in any manifest. Here is the workflow, the SPDX expression logic behind it, and the places it still gives wrong answers.
General
11 min
A former CTO walks through the exact pipeline he uses to screen take-home submissions for AI-generated code: three stacked signals, the thresholds he can defend in a candidate conversation, and the failure modes nobody warns you about. Concrete numbers from 214 submissions across three clients.
General
10 min
Take-home exercises have become the most reliable place to catch AI-generated code in a hiring pipeline, but almost no team uses the three signals they already own. A staff engineer's screening routine, the code tells that survive a careful read, and the legal questions nobody has answered yet.
General
12 min
Eleven of the 43 files I flagged as machine-written last fall belonged to students who had never opened a chat window. This is a step-by-step account of the calibration I now run every August: human baselines, per-file scoring, and a combining rule that cut my review queue from 214 to 61.
General
13 min
We ran an AI-origin detection gate on 1,847 pull requests over 90 days and hand-reviewed a 300-PR sample to find out what these detectors actually catch. The statistical scorers everybody buys landed at 26% precision. Stacking four signal families got us to 65%. Here is the pipeline design, the numbers, and an evaluation matrix for picking a vendor.
General
12 min
A working build guide to the similarity pipeline behind most academic code checks: tokenization, k-gram fingerprinting, winnowing, and AST shape comparison in roughly 300 lines of Python. Includes the threshold calibration table we used across six assignments and an honest account of where a homegrown checker stops being enough.
General
10 min
Pasting from Stack Overflow is the most common form of web code plagiarism, and peer comparison tools like MOSS will never see it. Here's how token fingerprinting actually matches a submission to a 2013 answer, how to read a web match report without overreacting, and why "Stack Overflow is public domain" is the most expensive misconception in the room.
General
8 min
Most departments escalate on a single number and regret it. Here is the five-step process I hand faculty who are sitting on a pile of flagged submissions and a Friday deadline, including the two steps that settle more cases than any detector.
General
17 min
Five generations of code similarity detection have each been beaten by a student with a text editor. This is the technical history of how detectors moved from byte comparison to tokens, fingerprints, syntax trees and learned vectors, and what that arc tells you about choosing a tool that can still find a match when the code has been renamed, refactored, or generated by a model.
General
12 min
A department ran a web-source scan on 412 intro Python submissions and got 61 hits, 23 of which were noise. This is the eight-step workflow they built afterward, from normalizing LMS exports and budgeting GitHub's code search rate limit to ranking matches by token count instead of percentage and assembling an evidence packet that survives an appeal.