Notes tagged
tempo
18 notes on tempo. All notes.
The complaint names the wrong thing
One link was reported broken twice in a single day. Nothing was ever wrong with that link. Two unrelated faults were eating clicks and looked identical.
Capitals are a contrast, not a volume
One line of styling put a whole application into capital letters. It read as deliberate for about a week, and after that it just read as shouting.
Written, and never wired
The code to undo a wrong stock entry already existed and had no callers. Nobody had asked for the button, because a workaround was already doing the job.
Filed as chatter
A document was waiting on one person's signature, and the request reached them as a line in a digest. Not a training gap. A row in a routing table.
A fact that had no owner
A payment made in instalments was invisible to half an application, because one plain fact was being worked out separately by every screen that needed it.
Why staged payments break accounting systems
Most systems store one paid date per bill. A payment in stages never writes it, so every screen asking "is this paid?" goes blind on exactly the biggest orders.
Paying less than agreed is a statement, not a typo
A short payment carries a decision inside it. If the system accepts the smaller number silently, the decision is lost and only the discrepancy survives.
Matching a bank line to the thing it paid for
A bank statement gives a date, an amount and a scrap of text. Turning that into "this paid that invoice" is a guess, and the rules around the guess matter.
WhatsApp is the interface, whether you designed for it or not
On Indian construction sites the real reporting system is a group chat. Fighting that costs years; reading it properly takes a few weeks and works immediately.
Attendance on a site with no signal
An attendance system that needs a network will be wrong on exactly the days it matters. Queueing punches is easy; the rules that keep the data honest are not.
A site photograph is a record, if anything reads it
Thousands of site photographs are taken every month and almost none become records. The bottleneck is not capture. It is that nothing ever looks at them.
Work slips before it is late
By the time a task is overdue, the decision that made it late was taken weeks earlier. The signals were all present and none of them were being counted.
The voice note is the report
A site engineer sends a voice note because his hands are dusty and the screen is in the sun. For years ours were stored as blobs that nobody ever opened.
The machine proposes, a person decides
An automatic link that turns out wrong is not just an error. It is an error that looks like a record, and nobody reading it later can tell nothing was agreed.
Offline-first is a data decision, not a network one
Queueing requests is the easy part. Offline changes what a record means, because it was created by a device nobody was watching, at a time nobody can verify.
One outage should be one ticket
Systems that raise an alert per symptom flood at exactly the moment attention is scarcest, and the flood is usually one cause wearing many names.
An import you cannot reverse is an import you should not run
Bringing history into a live system is a one-way door unless you build the way back first. Two properties make it safe, and both are cheap before the write.
A test that describes the code will defend a bug
A regression test anchored on how the code works, rather than on the rule it is meant to enforce, will guard a defect as loyally as a feature — and report green.