Persist the next eligible attempt instead of sleeping in a worker
A durable retry time lets the scheduler pause one provider scope while other work continues. Preserve the original operation identity across attempts.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 6 of 29
Preserve business identity when a message is redriven
Queue metadata can change during recovery. Put the durable operation identity in the application message and use it at the effect boundary.
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 articleWire field errors to the controls they describe
Keep labels, hints and validation messages connected in the document. Then handle focus and submission state so users can recover without losing their answers.
Read articleShare table state before building a separate mobile view
Put filters, ordering and selection above the presentation layer. Desktop rows and mobile summaries should act on the same identified records.
Read articleResume a draft through an explicit recovery state
Keep reauthentication out of generic mutation retries. Record the work to restore and validate its owner before returning the user to the task.
Read articleBuild a small judged query set before tuning weights
A reproducible search harness needs query intent, document judgments and versioned configuration. Start with a useful baseline rather than a large unreviewed benchmark.
Read articleMake the dependency diff part of the change review
Capture resolved packages and execution changes before building the release. Keep exceptions and artifact evidence connected to the same review.
Read articleBuild a permission matrix from the worker's operations
Turn application behaviour into specific allowed actions, then test the identity that will actually run the service.
Read articleBuild an incident record with a live summary and an append-only timeline
Keep the current operating picture easy to find while preserving how it changed. Link actions to owners and evidence rather than burying them in narrative updates.
Read articleTurn the retention schedule into destination-specific work
Separate eligibility from execution and track each copy. A resumable workflow makes partial deletion visible instead of hiding it behind one database status.
Read articleRevoke access while an answer is still cached
A permission test should include the period after access changes. This walkthrough checks fresh requests, cached answers and conversations that were already open.
Read articleAlmost the same product code is the wrong product
Similar manuals are a useful stress test for semantic retrieval. Build examples where a one-character difference changes the correct answer.
Read articleTest the table that continues on the next page
Multi-page tables expose mistakes that ordinary paragraph tests miss. Check the relationship between a value, its column heading and the note that qualifies it.
Read articlePlant a real citation beside an unsupported exception
A useful citation test uses a relevant source and a subtly wrong answer. This exposes failures that broken-link checks cannot find.
Read article