Nine each morning is not a fixed UTC interval
A local business schedule needs a named time zone and explicit daylight-saving behaviour. Store the user's intent before calculating individual execution times.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
40 articles in Australian technology
Page 1 of 3
A field report can be saved without reaching the office
Design offline work around a durable draft, an identifiable submission and a server receipt. Each answers a different question for the person holding the phone.
Read articleA correct map pin can still be the wrong delivery address
Separate physical location, postal destination and service instructions. One address field cannot reliably carry all three meanings.
Read articleTwo decimal places do not define a money model
Separate currency, calculation precision and the point where an amount becomes payable. Display formatting cannot repair an ambiguous rounding policy.
Read articleStore the schedule rule and the next occurrence separately
Preserve local intent so future executions can be recalculated correctly. A single timestamp cannot explain a recurring business schedule after an edit or time-zone change.
Read articleBuild the submission queue before adding a sync spinner
A reliable offline implementation records intent before sending, keeps attachments recoverable and clears pending work only after saving a server receipt.
Read articleStore an address without throwing away the unit number
Build entry, matching and downstream formatting around explicit components. Preserve the user's confirmed destination when a provider normalises its spelling.
Read articlePut currency and scale in the API contract
Make amount representation explicit from input to storage to payment. A named conversion prevents a correct number from acquiring the wrong unit.
Read articleTest the clock time that does not happen in Sydney
Daylight-saving boundaries reveal hidden scheduling defaults. Use a known transition and assert the product's chosen gap and overlap behaviour.
Read articleClose the app after the server accepts the report
The hardest offline test is a successful server write with no receipt on the phone. Reopening must recover that result without submitting the work twice.
Read articleTry the address your autocomplete refuses to find
Address tests should cover manual entry, partial matches and downstream truncation. A list of familiar suburban houses leaves important failures untouched.
Read articleTest the half-cent before testing the million-dollar invoice
Small boundary values expose rounding defects that large round numbers conceal. Exercise scale, signs, allocation and serialisation together.
Read articleMeasure scheduled work against its intended occurrence
A job's eventual success does not show that it ran at the right business time. Track due occurrences, delay and duplicate effects separately.
Read articleCount unsent field work, not just successful requests
Sync health needs the age and outcome of business submissions. A fast API can coexist with reports that have been waiting on phones for days.
Read articleA high address-match rate can hide failed deliveries
Measure whether people finish the address task and whether downstream work uses the intended destination. Provider matches alone are an incomplete success measure.
Read articleA money calculation should reconcile to the cent
Acceptance starts with invariants and explainable differences. An average error close to zero can hide offsetting mistakes across individual transactions.
Read articleA scheduled job ran an hour late
Compare the stored local rule, named zone and resolved instant before changing the server clock. The error may be in interpretation, queueing or display.
Read articleResolve a field conflict without losing the technician's notes
A sync conflict is a disagreement between versions, not a network fault. Preserve the local work, compare the changed fields and record the chosen resolution.
Read article