One field, two questions
An invoice undercharged a school by 32,000 dalasi a year. A WhatsApp link dialled a number that doesn’t exist. A teacher who takes both Maths and English with one class couldn’t be recorded at all.
Three unrelated symptoms. One mistake, three times.
A fee’s recurrence was answering does this repeat? and what period does
its price cover? — so an annual bill charged a per-term fee once, because the
multiplication had nowhere to live.
A phone’s number held the country code, while a code field held it too —
so the code got recorded twice and the link dialled 2202203000137.
A class teacher’s role answers do they own this class? and what do they
teach here? — so a duplicate guard that is correct for the first question makes
the second one impossible to express.
Each time the fix was the same: split the axes. And each time, once split, the logic that had nowhere to live simply appeared — one owner per class and many subjects, a price and a period, a code and a number.
The signature is worth memorising, because it’s visible before the bug is: when one field answers two independent questions, some necessary rule has nowhere to be written down. It doesn’t vanish. It gets smeared across call sites, or silently dropped, and you meet it later wearing a costume.