Correct the destination without moving the wrong job
Address support needs to identify the role, revision and affected work before applying a correction. A profile edit can otherwise change more than the customer intended.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
40 articles in Australian technology
Page 2 of 3
Investigate a one-cent mismatch without editing the balance
Trace the original inputs, rounding policy and provider units before applying a correction. A manual balance change can conceal the defect and break later reversals.
Read articleRecover local intent before replacing fixed-offset schedules
Existing UTC timestamps may not reveal what users originally meant. Classify schedules before converting them to named-zone recurrence rules.
Read articleAn app update must carry yesterday's unsent jobs
Offline upgrades need compatibility across local storage, queued commands and the server. A new screen is not ready if an older submission becomes unreadable.
Read articleSplit a legacy address field without inventing its components
Moving from free text to structured addresses is a data interpretation task. Preserve the original, isolate ambiguous records and avoid turning guesses into verified locations.
Read articleReplace floating-point amounts without rewriting history
A decimal migration must distinguish representation cleanup from a change in financial meaning. Preserve original evidence and reconcile differences before switching readers.
Read articleA queued schedule should not preserve revoked authority by accident
Scheduled work can run long after a user creates it. Define whether execution uses current requester rights or an explicitly authorised organisation process.
Read articleA shared tablet must not submit the previous user's work
Offline records need an account boundary that survives logout, reconnection and staff changes. Local possession of a draft does not establish current permission to submit it.
Read articleAn address lookup can reveal where your customers work
Review the information sent to lookup providers and stored in diagnostics. Address assistance should not quietly export access notes or unrelated customer details.
Read articleThe client can propose a price, but the server must authorise it
Amount validation includes who may choose the inputs and change the result. Correct decimal arithmetic does not protect an endpoint that trusts an editable browser total.
Read articlePlan for the burst at the start of the business day
Local-time schedules can concentrate work even when the daily total is small. Spread only the tasks whose timing promise allows it.
Read articleSize offline sync for the depot's morning reconnection
Average traffic hides the burst when many devices reconnect together. Separate small business commands from large files and budget for retries without multiplying work.
Read articlePay for useful address lookups, not every keystroke
Reduce unnecessary requests while keeping manual entry usable. Cache strategy and provider selection should follow the address task and data permissions.
Read articleExact arithmetic is usually cheaper than unexplained corrections
Choose numeric precision around the workload, then measure it. Do not trade away reproducibility before confirming that amount calculation is a real performance bottleneck.
Read articleReview dates, instants and durations as different data types
A calendar date, a local appointment and an elapsed interval answer different questions. Converting them all to timestamps can change their meaning.
Read articleAsk the offline demo to prove where the report lives
Review persistence and recovery at each boundary. An attractive offline screen says little about whether work survives a crash or reaches the right account.
Read articleReview the address after it leaves the form
The highest-risk defects often appear in labels, exports and job creation. Trace a difficult address through the complete workflow before approving the component.
Read articleAsk the calculation to explain its last cent
Review types, rounding boundaries and external units as one design. Most amount defects appear where two individually reasonable components disagree.
Read article