Limit Compared In Wrong Unit

What goes wrong

A numeric limit set in one unit or quantity is compared against a value measured in another — dollars against cents, a gzip budget against uncompressed size, a byte limit against a character count — so the check is too strict or too lax by a conversion the code never applies.

Example

A 500 KB gzip budget is checked against the uncompressed bundle size, so every build fails the check although the shipped file is 180 KB.

Not to be confused with

The stored value itself is right, unlike Quantity Written In Wrong Unit where the value is saved in the wrong unit; and not two spellings of one value compared as unequal (Equivalent values compare different).

Discovered by

@sks24git GitHub

Field notes · 4

@sks24git2026-09-23beat 3 review rounds

A deleted guard was replaced by a cap on the finished value instead of on the input. The cap used the wrong unit and a sibling number still read the raw input, so the safety reserve silently vanished.

Name the replacement when you delete a guard. Else you reinvent it once per round, wrong in a new way each time.
Bound the input, not the output. Capping one result leaves its siblings raw.

@sks24git2026-09-10beat 2 review rounds

The new counterpart compared a stored net balance against a gross sum of debit legs. An account holding a positive lot and a small debt then raised a permanent false alarm.

Compare net with net. Name the sign convention of both sides before you subtract them.
A check that cries wolf forever gets muted, and then it is not a check.

@sks24git2026-09-10beat 1 review round

A cleanup kept the branch guarded by a flag and deleted the other one. Every caller had already forced that flag true, so the surviving arm is the dead one and the deleted arm was the only path top-ups ever took.

Prove a branch dead from its callers, not from its condition. Inside one function a flag is whatever the callers already fixed.

@sks24git2026-09-04

A health check that had never done I/O was given one database query so a monitor could read a size. The probe's timeout equals the pool's connect timeout, so a slow database now pulls every instance out of rotation.

The liveness path does no I/O. A dependency's slowness must never look like your process is dead.
Measure in the background, serve a memo. A stale number beats a blocked probe.