Two possible paths lead to their cheating code getting into a release. Either it was added by coding agent and no one looked at it, bad, but worse would be that a person was aware of it and approved - that's malicious.
Either way you don't want to be platforming the product because neither shows any degree of responsibility.
You joke but when benchmarking with ai this is important. When you tell it optimize X, it will do so at any cost, including cheezing benchmarks. So you have to make sure you tell it what it can’t optimize along with what it can.
Should be outright banned as a precaution.
Two possible paths lead to their cheating code getting into a release. Either it was added by coding agent and no one looked at it, bad, but worse would be that a person was aware of it and approved - that's malicious.
Either way you don't want to be platforming the product because neither shows any degree of responsibility.
Or the third explanation is we didn't cheat: https://news.ycombinator.com/item?id=50209450
where's the sourcecode for 0.4-preview?
3 replies →
https://news.ycombinator.com/item?id=50210444
17 replies →
Hope the ClickHouse maintainers stand their ground and do not let pgrust back in until it and the maintainer has matured more.
Love the confidence and complete lack of acknowledgement of the initial fuck up.
Maintainer of pgrust trying to get it merged in is insane
written with claude lol
Did they ask Claude "don't cheat" this time round?
You joke but when benchmarking with ai this is important. When you tell it optimize X, it will do so at any cost, including cheezing benchmarks. So you have to make sure you tell it what it can’t optimize along with what it can.