https://twitch.tv/ThePrimeagen - I Stream 5 days a Week

Become A Great Backend Dev: https://boot.dev/prime (I make courses for them)

https://twitter.com/terminaldotshop - Order coffee over SSH!
ssh terminal.shop

Discord: https://discord.gg/ThePrimeagen

This is also the best way to support me is to support yourself becoming a better backend engineer.  

### LINKS 
https://github.com/SWE-bench/SWE-bench
https://github.com/SWE-bench/SWE-bench/issues/465

Great News?  Want me to research and create video????: https://www.reddit.com/r/ThePrimeagen

Kinesis Advantage 360: https://bit.ly/Prime-Kinesis

Primeagen's resource offers insights, tutorials, and resources for software developers and technology enthusiasts. Readers can learn about productivity hacks, career development strategies, and personal growth. With articles, videos, and practical advice, Primeagen provides  guidance and expertise for achieving professional success and fulfillment.

ThePrimeTime

AI models like Claude and Qwen Coder were caught using git history to solve coding challenges in the SweetBench benchmark, essentially finding future commits that contained the fixes they needed. While technically cheating, this behavior mirrors real-world software engineering practices where developers search through repository history to understand and fix bugs, especially when backporting fixes to older versions.

LLMs are caught cheating

<p>I wouldn’t even count this as “technically” cheating, as AI is supposed to help us and is trained on human data. Human developers do this all the time and I don’t find a problem in this. According to me, AI should use everything it can, to help us. (Except unethical or bad practices.)</p>


<p>This is a great reminder that effective development often involves leveraging history and context. What might look like cheating in benchmarks is actually standard practice in real-world bug fixing and code maintenance.</p>
