-
We re-ran our scheduling guides with a proof, and some of their lessons changed
Re-derived with proven-best rosters: a 10-hour rest gap costs a café nothing, two weekend requests are free, and tough shifts even out exactly.
-
Could the call-out rebuild have moved fewer people? An exact answer on 41 weeks
An independent integer program finds the fewest late changes after 41 call-outs. The default rebuild matches it on all 41 once the caller counts too.
-
Someone called out. Rebuild the week, but don't move the people who showed up
After a call-out, a rebuild that keeps the posted shifts made half the late changes of a free rebuild: premiums halved, same hours left open.
-
The roster was right; the proof was 2 hours short
Two call-out weeks the rota builder could not prove came down to arithmetic: with 3, 8 and 10 hour shifts, nothing leaves exactly 2 hours open.
-
Prove first, polish later: a 40-person staff roster checked in 10 seconds
Timing each stage of the roster builder's exact check found two passes the proof made redundant. 40-person weeks: 15-57 s to 6-12 s, all proven.
-
Fixing a call-out without reshuffling 60 people
Rebuilding after one call-out moved 1,623 shifts over 24 call-outs on 60-person weeks. Keeping posted shifts and starting from them cut it to 76.
-
Planning a month of shifts: the planner was solving the same week four times
A longer search budget proved no more weeks of a 4-week staff plan. The waste was rebuilding identical weeks; reusing them halves the time, same rotas.
-
The floor was free: proving two staff schedules in 1.7 seconds instead of 19
A staff scheduler took 19 s to prove two call-out weeks. Most of it went on finding a 3-hour floor that a 0.05 s LP plus whole-shift rounding gives.
-
Fifty-one changes where two would do: checking a scheduler against an exact solver
On a 60-person week, one call-out made our rebuild move 51 shifts. An exact solver showed 2 were enough. The missing move: trade up to the longer shift.
-
Three eighths of a shift: why a staff scheduler couldn't prove a roster it had already found
Two call-out weeks stayed bounded because the pay LP left part of an 8-hour shift open instead of a whole 3-hour lunch. One extra LP row proves both.
-
Two closers on Friday, one on Tuesday: a lock-up rule by weekday
A two-to-lock-up rule every night cost a real bakery 45 staff hours a week. On Friday and Saturday only it cost 10.
-
Who locks up? Cleaning after close, and what a two-person rule costs
90 minutes of cleaning after close is one person staying two hours. A two-to-lock-up rule cost a bakery 28 hours a week where one closes, 0-7 where two are on.
-
Grouping 10,000 burst frames took 34 seconds; a pigeonhole index makes it 0.4
ShootFlow compared every pair of photo hashes to group burst frames. Splitting the 64-bit hash into 9 blocks finds the same groups 78x faster on 10,000 photos.
-
ShootFlow's overnight pipeline now develops Canon CR2, picking the right profile per camera
Put your camera's .dcp profiles in a folder and ShootFlow's overnight pipeline turns CR2 files into 16-bit masters, refusing rather than guessing a profile.
-
Square and Toast exports read fine and gave quietly wrong numbers
Two US till exports parsed without an error, but one staffed from gross sales and the other counted voided lines. Both are fixed.
-
Stale or just slow? Telling a frozen data feed from a series rounded to its precision
A repeated value can mean a stale feed or a series rounded to its precision. A tick check tells them apart, tested on simulated and real data.
-
Sticky series: the changepoint the data itself hides
Why a real level step goes missing when a series repeats stale values, and why the fix we planned next could not have helped. Pre-registered, with the numbers.
-
Synthetic control in a browser tab, and how the placebo screen changes the p-value
A free synthetic control tool reproduces the West Germany weights. On the same data the placebo p-value runs from 0.059 to 1 on one screening choice.
-
A hard stop is only a stop if nothing hits first
Adding end stops to the tennis feeder's turntable showed the head would hit the hopper posts 4 degrees before reaching them. Two sets of posts moved out.
-
A home switch that says which side you're on
Drawing the tennis feeder's home switch showed the firmware took any closed switch as home: a head left 3 degrees past it aimed 1.3 m wide.
-
The authorised NF-e that corrected the formula: 35 real files against an NF-e checker
We ran the new NF-e checker on 35 open-source NF-e files. An authorised import invoice leaves the duty out of vNF, so the checker now accepts both readings.
-
The bank headers we wrote from memory were wrong: 22 real US exports through the importer
Run through ai-bookkeeper's importer, 22 public US bank exports gave four faults. The Navy Federal, Truist and TD headers written from memory were all wrong.
-
The clear favourite that was a coin flip
Quick Pick called a clear favourite for three respondents in four, wrong in over half. A refit of each person's answers fixes the intervals and the claim.
-
The tone curve 68 camera profiles share is Adobe's default, and 20 numbers redraw it
68 of RawTherapee's camera profiles embed one 8,192-point tone curve. It is Adobe's ACR3 default. A 20-knot spline fit gets within 0.08 of an 8-bit step.
-
The dead sensel and its four diagonals: repairing a DNG's bad pixels before the demosaic
ShootFlow's DNG developer now runs the two bad-pixel opcodes. A dead sensel becomes the mean of its nearest same-colour neighbours, exact on a plane.
-
The discount for filing on time: 15 more states, read from their own forms
Most states let sellers keep a slice of sales tax for filing on time. We read 19 states' own rules, and found a CLI bug that ignored --state.
-
The gap was in the ruler: our raw developer against LibRaw, measured properly
ShootFlow's Canon renders looked 3-9% brighter than LibRaw's. The developer was fine: our check passed LibRaw a white level with black still in it.
-
The idle time was a missing cache: timing every phase of our site build
A profile said our site build was idle 57% of the time. Timing each phase traced that to a missing cache; then three small changes cut 4 to 5 s.
-
Two sessions, one speed-up: what a merge conflict said about our perf runs
Two agent sessions profiled the same league scheduler search on the same day and found the same fix. One landed first; the other kept a smaller 6% win.
-
The Leica told us how its lens bends, and its own preview confirms we listened
A Leica T DNG stores its lens correction as a WarpRectilinear opcode. ShootFlow now applies it, matching the camera's own preview to 0.18 px.
-
Sizing house water pipes with Hunter's rule, computed exactly
Free house water pipe sizing by Hunter's 99% rule, computed exactly. On a two-bath example the normal approximation picks a 3/4 in main; exact needs 1 in.
-
The phone wrote down its own vignette, and we weren't reading it
Android phone DNGs store lens shading as GainMap opcodes. ShootFlow now applies them; three real camera DNGs match LibRaw within a tenth of a step.
-
The replay ran out of rows, not the guard: a metric watch that waits for a second look
A metric-watch guard failed its test by one change, first seen on the replay's last row. Scored fairly, it passes narrowly and is now the default.
-
The same line whatever the knots: a quarter off our trend-bend search
Every fit in our trend-bend search began by removing the same line. Doing that once, and each knot set once, cut a quarter of the time with identical output.
-
A league scheduler 27 times faster, with the same schedules to the last bit
The multi-division league scheduler spent 50 s in one fairness sweep. Tabling the costs once per night cut it to 1.85 s and every schedule hashed the same.
-
The schedule search that recounted numbers it already knew
The league scheduler's carry-over search recounted costs nothing had changed. Caching them made it faster, with every schedule hashing the same.
-
The season between the choices: letting a league organiser pick from the whole frontier
The league scheduler's four fixed choices skipped stretches of the carry-over / back-to-back trade. Now every frontier season is a button.
-
The shortest pick route is cheap to find, and batching matters more
A free pick route and batching tool runs the exact Ratliff-Rosenthal method. On invented orders, grouped carts cut walking about 71%; routing alone, 13%.
-
Saudi e-invoices put tax on every line, and our checker counted it twice
Reading every TaxTotal in a ZATCA invoice as the document's raised false tax errors on all 19 of ZATCA's good examples. Reading only the root fixed it.
-
The UAE line amount that no rule checks
PINT UAE makes every line state its VAT and amount payable, but no rule checks they add up. We added INV-060 and tested it on seeded faults.
-
The workflow file nobody tested: a lost-state race in a self-hosted metric watch
Replaying a scheduled GitHub Actions workflow over 20 simulated days found a push race that would have re-sent the same alert. The fix is four lines.
-
The worst case for a beam over three posts is not every span loaded
On two equal spans, live load on one span gives 36% more sagging moment than on both, and lifts the far end. A free tool finds the worst pattern exactly.
-
TD07, TD08, TD09: Italian invoice codes the FatturaPA schema refuses
Our FatturaPA checker passed TD07-TD09 and failed invoices with two withholdings. Moved to the spec 1.9 schema (XSD 1.2.3), it now agrees with xmllint.
-
We read 26 state tax pages. Hawaii's annual return is in April, and Iowa dropped prepayments in 2022
Sales tax due-date presets from guides, checked against 26 states' own pages: two were wrong, and several states don't offer the frequencies people ask for.
-
Two more instructions a raw file can carry: vignette and value maps
ShootFlow's DNG developer now runs FixVignetteRadial and MapPolynomial, checked against the formulas. No real camera file carrying them has turned up yet.
-
UAE e-invoices state every line's VAT twice, and our repair button ignored the second one
UAE e-invoices restate each line's VAT and amount payable. Of 76 we planted wrong in OpenPeppol's examples, the repair fixed none; now it fixes all 76.
-
Unwrapping a fisheye DNG: what the WarpFisheye opcode asks a raw reader to do
ShootFlow now runs the DNG WarpFisheye opcode. What its four terms mean, why an ideal fisheye reads radius atan(r), and what we could and could not check.
-
"We're not interested" stopped, "We are not interested" didn't: one contraction in a sales agent's rules
A guard written for other people's no also caught the writer's own. The fix was one lookbehind, checked on 76,565 real Enron replies.
-
Checking a Mexican waybill: what 322 public Carta Porte files showed
A free offline check for Mexico's Carta Porte 3.1 waybill, run on 322 public CFDI files: 21 schema-valid, and a bug in our own decimals check.
-
What a camera profile does to colour: 161 DCP profiles measured
ShootFlow now applies DNG/DCP hue/saturation maps and look tables. Across 161 real profiles, the median turns saturated hues 10 degrees and adds 27% saturation.