Alex focuses on refactoring-resistant similarity detection and benchmarking Codequiry against tools like MOSS, JPlag and Dolos.
Tutorials
12 min
Alex Petrov
•
3 months ago
A step-by-step guide to building a source code similarity detection pipeline from scratch. Covers tokenization, AST comparison, Winnowing fingerprinting, and heuristic scoring. Includes working Python code and configuration strategies used by universities and enterprises.
General
6 min
Alex Petrov
•
4 months ago
We treat open source licenses like a tax code to be audited, scanning for SPDX tags and copyright headers. This legalistic approach is creating compliant but ethically bankrupt software. True compliance isn't about checking boxes—it's about understanding and honoring the social intent behind the GPL, MIT, or Apache licenses. It's time to scan for spirit, not just the letter.
General
8 min
Alex Petrov
•
4 months ago
Most static analysis tools flag trivial style issues while missing the architectural rot that cripples productivity. This guide shows you how to detect the five structural code smells that genuinely predict development slowdowns and defect clusters. We'll walk through real code, build custom detection rules, and integrate findings into your CI/CD pipeline.
General
6 min
Alex Petrov
•
4 months ago
A 2024 study of 12 million static analysis warnings found that the majority of flagged "code smells" have zero correlation with actual defects. We're drowning in false positives, wasting developer time, and missing the real architectural rot. It's time to audit your tool's configuration before it audits your team's productivity.
General
5 min
Alex Petrov
•
5 months ago
Web code plagiarism isn't just about student assignments. It's a rampant, costly problem for businesses. Competitors routinely lift unique CSS, JavaScript architectures, and even entire page structures. Here’s how to find out if it’s happening to you and what to do about it.
General
9 min
Alex Petrov
•
5 months ago
Your software is built on a foundation of open-source code you didn't write and licenses you haven't read. A single incompatible license can trigger lawsuits, force product recalls, or mandate open-sourcing your entire codebase. This isn't a theoretical risk—it's a daily operational hazard that most engineering teams are blind to.
Academic Integrity
7 min
Alex Petrov
•
5 months ago
When a single, cleverly obfuscated code submission exposed the limitations of traditional plagiarism checkers, Stanford's CS106B had a crisis. The incident forced a complete re-evaluation of how to teach and enforce code integrity in the age of GitHub and AI. This is the story of how they rebuilt their defenses.
AI Detection
7 min
Alex Petrov
•
5 months ago
AI code detection reports a 95% match. Your gut says it's wrong. You're probably right. This guide shows you how to move beyond the confidence score and conduct a forensic code review that separates AI-generated patterns from legitimate student work. We'll walk through three real student submissions from UC Berkeley's CS 61A course and show you exactly what to look for.