Correctness
Behaviour matches the agreed specification, and the specification is written where both sides can read it.
About the company
An IT practice built around clarity
SPOONER & SONS GAS & HEATING LTD works in information technology: designing, building, integrating and maintaining software systems. This page describes how that work is approached, without claims that cannot be evidenced.
§ 01Company overview
What the company does
The company provides technology services across the life of a system: understanding a problem, designing an approach, writing the software, connecting it to the systems around it, verifying it, releasing it and looking after it afterwards.
Engagements vary in size. Some are a single well-defined component; others run over longer periods and cover several parts of an organisation's technical estate. In every case the scope, assumptions and deliverables are written down before implementation starts.
No history, certifications, awards or client names are presented on this website because only information that can be verified is published here.
§ 02Technology focus
Where the technical attention goes
Applications
Software that encodes real operational rules — records, workflows, calculations, permissions — built so those rules stay legible in the code.
Web platforms
Browser-delivered products and content systems, with accessibility, performance and metadata treated as requirements rather than afterthoughts.
Cloud environments
Infrastructure defined in configuration, with repeatable deployment, monitoring and documented recovery procedures.
Data movement
Integration and automation between systems, with validation, retries and honest error reporting instead of silent failure.
§ 03Working principles
Principles that guide the work
- 01
Understand before building
Time spent framing a problem is cheaper than time spent rebuilding a solution to the wrong problem.
- 02
Prefer the simplest structure that works
Complexity is added only when a concrete requirement demands it, and is documented when it is.
- 03
Make state and failure explicit
Systems are designed on the assumption that networks, dependencies and inputs will sometimes misbehave.
- 04
Automate anything repeated
Builds, tests, deployments and routine data tasks are scripted so results do not depend on who runs them.
- 05
Leave a readable trail
Commits, notes and documentation are written for the next person to open the project.
§ 04Collaboration approach
Working alongside a client team
Clients keep ownership of the decisions that belong to them: priorities, budget and acceptance. The company's responsibility is to make those decisions well informed.
- A single written record of scope, assumptions and open questions, kept current.
- Regular demonstrations of working software rather than status percentages.
- Direct communication about risk, including the risks of doing nothing.
- Handover material prepared as work proceeds, not assembled at the end.
§ 05Engineering values
What good work looks like here
Maintainability
Another engineer can understand, test and change the system without a guided tour.
Proportion
Effort matches the value and risk of the problem; no gold-plating and no shortcuts on critical paths.
Transparency
Progress, cost and difficulty are reported as they are.
Restraint
Fewer dependencies, fewer moving parts, fewer surprises in production.
Care for users
Interfaces are judged by whether people can complete their task, not by novelty.
§ 06Contact
Getting in touch
SPOONER & SONS GAS & HEATING LTD
Displayed as plain text; this website contains no links or buttons.