Check whether the work exists before asking for another submission
After an expiry complaint, distinguish missing confirmation from missing data. Preserve the draft and verify the original command before retrying.
Read articleAI implementation, software architecture, cloud operations and Australian technology policy.
40 articles in Web applications
Page 2 of 3
After an expiry complaint, distinguish missing confirmation from missing data. Preserve the draft and verify the original command before retrying.
Read articleCheck eligibility, ingestion and query interpretation before changing ranking. A score adjustment cannot retrieve a document that never entered the candidate set.
Read articleA form redesign changes data and navigation as well as appearance. Map saved answers, validation rules and return paths before introducing the new flow.
Read articleA new data component can alter selection, query state and keyboard behaviour. Preserve those contracts deliberately during the migration.
Read articleAuthentication updates meet old clients, existing cookies and unfinished work. Test the transition as a mixed-version system before changing production policy.
Read articleCompare candidate coverage and ranked results under the same access context. A successful reindex does not establish equivalent search behaviour.
Read articleForm accessibility and data handling meet in the same workflow. Clear questions, scoped drafts and safe error messages reduce both confusion and unnecessary exposure.
Read articleReview the server response, exports and row actions as well as visible columns. Responsive presentation is not an authorisation boundary.
Read articleReauthentication proves an identity now. It does not automatically authorise an old action or transfer a previous user's saved work.
Read articlePrivate documents should never compete for visibility with public results. Evaluate ranking only after the access model defines what the user may receive.
Read articleCompare the cost of collecting a field with the value it adds to the next business action. More mandatory information can create more support work rather than better requests.
Read articleSeparate the cost of fetching, sorting and displaying records. Choose pagination or virtualisation for the stage that actually limits the task.
Read articleCoordinate recovery across concurrent requests and measure the full return-to-task path. Repeated refresh attempts add load without restoring work faster.
Read articleMeasure the quality gained by each retrieval stage against its latency and operating cost. More candidates and more models do not automatically produce better search.
Read articleEmpty, invalid and interrupted forms expose weaknesses that a completed demo hides. Assess the actual journey with keyboard, touch and assistive technology.
Read articleReal data stresses width, identity and navigation. Approve the complete interaction rather than a tidy screenshot of short sample rows.
Read articleThe important questions are what survives, what may already have happened and who is allowed to continue after sign-in.
Read articleA credible relevance review shows regressions, unjudged results and corpus assumptions. A single improved demo query is not enough.
Read article