
Article · 2 min read
A backup you have not restored is a hypothesis
The only evidence that a backup works is having used it. Ask when yours was last actually restored.
01Service
Building and maintaining online shops for retailers in the United Kingdom. The work covers the catalogue and checkout, the systems the shop depends on, and the technical conditions that decide whether product pages are fast and findable.
What is delivered
02Deliverables
03Stages
Review the current shop, the systems around it and the records that exist. Produce a written scope with the catalogue model, integration list, URL disposition and the things explicitly excluded.
Incremental delivery on a staging environment with authentication, so nothing in progress is publicly reachable or indexable. Accessibility and performance are checked per template as they are built.
Freeze the URL map, test every redirect, verify canonical and sitemap output, and rehearse the restore. A migration that has not been rehearsed is not a plan.
Deploy, verify DNS, certificates and redirects from raw requests, then monitor errors, uptime and crawl coverage through the period when problems actually surface.
04Due diligence
These apply to any developer you speak to, including this one.
05Reading

Article · 2 min read
The only evidence that a backup works is having used it. Ask when yours was last actually restored.

Article · 2 min read
An alert nobody receives is a log entry with extra steps. Deciding who gets woken is part of the system design.

Article · 2 min read
A checkout that cannot be completed by keyboard excludes customers who were ready to pay. The same fixes reduce abandonment for everyone.
What you sell, the platform you are on and what is failing. That is enough to tell you whether this is worth taking further.