The Kluever Maneuver
Comments on “The Kluever Maneuver”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
In "The Kluever Maneuver," Jordi (the author) recommends splitting every bugfix into two commits: first a passing test that encodes the buggy behaviour, then the fix plus flipping that test to assert correct behaviour.
Why it ranked
No. 28 of 59 with a score of 0.60. The panel rated it highest on new information (0.90) and practical relevance (0.76), lowest on significance (0.39). Placed No. 28, No. 34 by score alone: the fifth Programming & dev tools story of the day (−0.040). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- A practical, well-illustrated software engineering tip on two-commit bugfixes and test-first bug reproduction; useful to builders but a minor, widely known practice with modest novelty.
- AI judgeJudge 3gpt-5.6-luna
- A clear, actionable testing and commit workflow with concrete examples. It is useful engineering practice, though not novel research and somewhat limited in significance; the examples contain minor presentation/code inconsistencies.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.60total under rubric v2.3
- Significance0.39
- Reader interest0.66
- Audience breadth0.65
- Practical relevance0.76
- Substantiated0.60
- Technical depth0.63
- New information0.90
- Counts against: Promotional0.03
- Counts against: Overclaim0.19
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.43 | 0.25 | 0.50 | 0.39 | 0.25 | +0.24 | +0.094 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.60 | 0.55 | 0.82 | 0.66 | 0.27 | +0.26 | +0.171 |
| Audience breadthHow many people who build technology does it concern? | 0.79 | 0.50 | 0.67 | 0.65 | 0.29 | +0.13 | +0.085 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.89 | 0.60 | 0.80 | 0.76 | 0.29 | +0.22 | +0.168 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.67 | 0.40 | 0.72 | 0.60 | 0.32 | +0.05 | +0.030 |
| Technical depthHow technically substantive is it? | 0.85 | 0.45 | 0.58 | 0.63 | 0.40 | +0.05 | +0.031 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.83 | 0.90 | 0.96 | 0.90 | 0.13 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.05 | 0.01 | 0.03 | 0.04 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.20 | 0.20 | 0.18 | 0.19 | 0.02 | −0.11 | −0.021 |
| Sum of contributions | +0.596 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.596 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-01/28/"><img src="https://rubric.hrih.si/badge/2026-11-01/28.svg" alt="Ranked #28 on Rubric, 1 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 7 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenCausal conclusion
Writing a failing-behaviour test in a first commit and the fix plus corrected test in a second commit gives demonstrable proof that the bugfix actually fixed the bug.
The article gives no link or citation for it.
The article says “Demonstrable proof that the bugfix actually fixed the bug”
The source says No source to compare with.
No source givenCausal conclusion
The two-commit approach keeps CI passing at every commit.
The article gives no link or citation for it.
The article says “CI still passes at every commit”
The source says No source to compare with.
No source givenCausal conclusion
Adding a test and a bugfix in the same commit can give false confidence if the test already passed before the fix and the fix did not work.
The article gives no link or citation for it.
The article says “what if the test accidentally already passed before the alleged bugfix and the alleged bugfix didn’t actually work? In that case the added test gives false confidence that the bugfix…”
The source says No source to compare with.
No source givenCausal conclusion
In the age-check example, the proposed off-by-one change to can_access is not a real fix, and the proposed test passes both before and after it, because the bug is in the age calculation.
The article gives no link or citation for it.
The article says “The bugfix isn’t an actual bugfix and the proposed test actually passes both before and after the proposed fix”
The source says No source to compare with.
No source givenCausal conclusion
The Kluever Maneuver would have prevented the faulty age-check fix from being accepted.
The article gives no link or citation for it.
The article says “The Kluever Maneuver would have prevented this”
The source says No source to compare with.
No source givenQuote
The technique is named after the author's colleague Kurt Kluever, who taught it to the author.
The article gives no link or citation for it.
The article says “Because my colleague Kurt Kluever taught it to me, and I immediately think back to him when I think of this technique”
The source says No source to compare with.
No source givenQuote
Kurt Kluever usually calls the technique "terrible tests".
The article gives no link or citation for it.
The article says “He usualy calls it “terrible tests”, as in “Jordi, can you please write a terrible test for this”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 2 pts, not on front page
Recorded for context only, checked 1 Nov 2026, 05:47 UTC. It played no part in the ranking.