Add a read-only drift check to the delivery workflow
Detect changes without automatically applying a correction. Give the owning team a useful difference and enough context to decide what should happen.
Read articleCobnex blogs / Global
Cobnex blog
AI implementation, software architecture and cloud operations for teams worldwide.
456 articles
Page 5 of 26
Separate release identity from feature exposure
Deploying code and enabling behaviour are related but different actions. Track both so an operator can tell what a request actually experienced.
Read articleCount accepted jobs that miss their completion deadline
Queue workers can look healthy while old work remains unfinished. Measure from acceptance to the required result, including jobs that never emit a completion event.
Read articleGive consumers a defined secret-refresh path
A credential loaded once at startup will not automatically follow rotation. Make refresh behaviour explicit and test it at the connection boundary.
Read articleSave the integration intent before sending it to Xero
A durable operation record gives retries and support a shared source of truth. Record the target organisation and expected request before making the external call.
Read articleEncode the field policy beside the mapping
Keep direction, authority and empty-value behaviour in one reviewed definition. Scattered conditionals make the same field behave differently across imports and live updates.
Read articlePut a durable inbox behind the webhook endpoint
Store verified event identity and processing state before returning success. Let workers handle slow business logic without losing the ability to retry.
Read articlePersist 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 articlePreserve 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 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 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 article