-
Down-weighting the people who disagree makes a big survey confidently wrong
Without a harness cap, weighting respondents by agreement helps twice as much against careless clickers and hurts a real minority twice as hard.
-
Filtering survey respondents by consistency picks the people whose answers spread out most
Planted easy questions made careless respondents easier to spot. Gating on them barely helped: the most consistent people have the most spread-out items.
-
Our survey ranking looked overconfident on long lists. The test harness was the problem
A simulation said one in ten clear calls on 150-item surveys were backwards. The ranking was fine: a cap in the harness counted unanswered items as votes.
-
The survey taker who gets bored halfway: finding the moment from answer times
A change point in each person's answer times, read against the whole panel at the same point, finds mid-survey click-through at almost no cost.
-
Half-careless survey takers have normal-looking times. Their fast answers don't
A per-person median time misses respondents who click carelessly on half their picks. Cutting each fast answer instead recovers most of the harm in simulation.
-
Re-dealing three rounds of a league at once: a 3-edge-colouring as a search move
Re-dealing the matches of three rounds, every legal way, cuts a 20-team league's carry-over 6-10% at the tightest break budget.
-
Reading a 7shifts schedule without a CSV export
The free roster builder now reads the 7shifts API: UTC times put back on the location's clock, open shifts counted as needed, close shifts ended at closing.
-
Reading chant transcriptions against the 1908 book by machine: one wrong note in 1,500
Chant Forge reads square notation off public-domain scans and checks GABC against it: five pieces agree with the Vatican books; one Te Deum note was wrong.
-
Reading When I Work's shifts without a CSV, and why its times are easier than 7shifts'
When I Work publishes its API definition, and its shift times carry their own offset. A second scheduler now feeds the free roster builder.
-
What real Square and Toast exports taught a staffing tool
We had only read Square and Toast exports as made-up rows. Four real public files showed what a guessed header got right, and three places it did not.
-
The remove-duplicates button finds about a third of them
A free browser tool for duplicate contacts. On the Febrl benchmark it finds 99.6-99.8% of true pairs; an exact name-and-postcode match finds 26-36%.
-
Italy's SdI allows a euro on the VAT base, not a cent
Read from the Agenzia delle Entrate's own specification 1.9: two of our FatturaPA tolerances were wrong, and SdI never checks the document total.
-
Seven chants a men's choir cannot sing in unison, and the one-phrase fix
Of 67 Gregorian chants in Chant Forge's corpus, 7 span one semitone more than tenors and basses can both sing. Giving one phrase to one section fixes every one.
-
Equally good weeks that are not equally good months
Which of several equally good weeks a staff planner posts decides what next week can do. A one-week look-ahead kept every hour and cut changes 71%.
-
A week of call-outs at a real roster's rates: keep the posted schedule, tell fewer people
At one firm's real call-out rates, rebuilding a posted week from scratch told 6 people a week of a change; keeping the posted shifts told 2.5.
-
Skipping the rebuilds a call-out doesn't need
Two exact short cuts and early stopping cut the call-out check from 419 rebuilds to 243 with the same schedule picked, so it now runs on the page.
-
Charging a manager for slack the team already had
A quick call-out risk check over-counted badly. Counting hand-over chains raised its precision from 53% to 67% and stopped 21 trades that bought nothing.
-
Five times faster on the sample week, and why the multi-week planner did not get the speed-up
Running the exact method before the search made fresh rosters 3.5x faster, same proven score on 80 of 80 weeks. Tied rosters still differ.
-
When nobody can cover, free someone who could
On a 20-person week where no single shift move helped, freeing a stand-in cut the measured call-out exposure from 113 to 68 hours for $35 of score.
-
Reissuing a posted schedule twice as fast, with the same schedule quality
Exact solver first, local search second: 570 posted-schedule reissues after a call-out ran 2.2x faster with the same score, changes and premiums.
-
The 25-hour gap that was never there
A 60-person week sat unproven at 300 open hours over a 275 h bound. The bound was the problem: a 1.3 s LP with clique rows proves the 300.
-
Three ties, not five: a roster counted twice, and a tie-break that changed nothing
Picking among tied schedules at every reissue of a posted week changed 0 of 983 reissues and took 14 times as long. A tie-counting bug turned up too.
-
Six equally good schedules, and the one a call-out hurts least
Equally good schedules differ by half in what one call-out costs. Picking the least exposed cut open hours 3.5% over 40 seeded weeks, with 16% more changes.
-
Sixteen pixels instead of four: what bilinear sampling costs a lens correction
On a Leica T frame, bilinear sampling in the lens warp threw away 27% of the fine detail. A Catmull-Rom cubic keeps all but 11%, at about twice the cost.
-
Splitting our slowest test file did nothing; remembering the last roster did
A 101 s test file looked like the long pole of a 149 s suite. Splitting it changed nothing: the suite was CPU-bound. Remembering repeat builds cut it to 132 s.
-
Stems from a browser tab: a 60-line ZIP writer and a sum check
Chant Forge's studio page now hands a producer phrase markers and per-part WAV stems in one ZIP, byte-equal to the command line, checked in headless Chromium.
-
STL decomposition in a browser tab, and the Mauna Loa CO2 cycle that grew
A free STL tool matches statsmodels to 1e-11. On 52 years of Mauna Loa CO2 it finds the seasonal swing grew about 0.09 ppm a decade, whatever the window.
-
Teaching a chant scanner to see a diamond
A dependency-free chant scan reader now tells a rhombus from a square (118 of 120 held out), and the 1908 Te Deum was read by eye: 637 notes, no differences.
-
Teaching a scan reader to see a quilisma, and testing it on pages it had never seen
Finding the saw-tooth quilisma in scans of the 1908 Graduale by counting notched rows: set on five chants, then 15 of 17 found on nine never-seen chants.
-
The trough that couldn't reach the hopper
Drawing the catch net's ball trough for the open tennis feeder showed balls end up 2.2 m below the hopper. The design note said they would roll in.
-
Stirring a tub of tennis balls without jamming one
The open tennis feeder's tub drains through a 75 mm hole for 67 mm balls, so a few balls can bridge it. A little geometry chose where the agitator's arms go.
-
Tensioning a 2.4 m ball-lift belt: 7.5 mm of travel, and a tension you can count by hand
The top pulley tensioner for an open tennis-ball lift: where 7.5 mm of travel comes from, why 10.5 N, how to set it by counting swings, and a flight fix.
-
The 1976 warming acceleration, dated and tested: why the test on differences missed it
A level test for a change of trend slope with AR(1) noise and a bootstrap p-value finds the 1976 warming acceleration at p 0.001; differences gave 0.80.
-
The alert hint on a second labelled set: 47 real server metrics, three pre-registered tests, three misses
Pre-registered on 47 real NAB series watched hourly: the alert hint, a drift lead and a new hint rule all missed. Level detectors sat near chance.
-
The audio cap that outlived its reason: 444 text-only runs and four stories you can hear again
A 400 MB audio cap written for GitHub Pages kept 444 story runs text only after the audio had moved to a CDN. Four new Kokoro readings, and the numbers.
-
The tennis feeder's CAD tests took 27 minutes because they rebuilt the robot 60 times
The tennis feeder's CAD check ran 19 of 20 CI minutes: an 18 s part build was requested ~60 times. A cache cut the suite from 1637 s to 323 s.
-
The choir's changes of singer were not cameos
A three-section chant split tripled changes of singer. A cost per entrance was meant to cut the short ones; on 67 chants there were almost none.
-
The colour fringe fits in fifteen terms
ShootFlow now corrects lateral colour from lensfun with distortion, exactly, as one DNG warp. Uncorrected, 30% of lens profiles leave a 1 px fringe.
-
The failed import that cost more than the copy: placing raw tiles on every core
Placing tiles on the decode threads made a Pixel 3 XL raw read 1.3-1.4x faster with numpy. Without numpy, a retried failed import made it slower.
-
The fastest cutting-stock solve is the one you already did
A framing takeoff re-solved every lumber size's cutting-stock problem on every edit. Keeping 128 recent answers made a test 4x faster, output identical.
-
The DNG flag that means 'skip it if you're in a hurry', not 'skip it'
ShootFlow skipped every DNG opcode flagged for full quality only, which is the opposite of what the spec asks. Fixed, and checked on six real camera DNGs.
-
The half that was eight percent: making a phone's raw file read twice as fast
A note blamed Python de-stuffing for half of a DNG tile's decode. A timer said 8%. Moving the whole tile into C made reads 2x faster, same sensels.
-
The RAW file read was the slow part: 4 seconds of bit unpacking, and a develop on every core
Threading a numpy RAW develop halved it on four cores, but the bigger cost was the file read: a per-sample Python loop, now 17x faster, same bytes.
-
The walk that never arrived: half a call-out check spent searching for a roster another stage finds in 20 ms
The rota builder's call-out check now runs 2.3x faster: 570 rebuilds with the same open hours, and retail's wait drops from 10 s to 1.5 s.
-
Twenty-two files in a circle, and none of them broke: a Rust import-cycle checker
A Rust checker built the same import graph as madge on 11,422 files in 0.2 s, not 14 to 18 s, and found 22 files on cycles. All of them load fine.
-
Two characters of regex cost us most of a second per build
A leading whitespace match stopped V8 scanning straight for '<'. Dropping it and trimming by hand made our share-tag pass 25% faster with byte-identical output.
-
Two versions of lensfun brighten the same corner differently
ShootFlow's lensfun vignetting port matches liblensfun 0.3.4. Lensfun's release and master still differ by up to 10% on steep lenses.
-
Two real staff schedules: one store rewrote its week, one firm worked its roster
Our schedule importer had only ever seen made-up files. The first two real exports it met, it refused. Fixing that turned up two very different posted weeks.
-
Two characters that refuse every month: what checking ISSNet and Betha NFS-e files taught the validator
The NFS-e checker now reads ISSNet 1.00 and Betha 1.00 schemas: 36 of 36 published files and 1,151 of 1,151 mutants match xmllint, after two fixes.
-
Two shops in one sales file: planned together, the second shop vanished
Planned as one shop, a two-site sales export came up 12 person-hours a week short and staffed nobody at the second site. Now each site is planned alone.