01
Software engineering
Design and implementation of applications that carry business logic, from data models through to interfaces.
Information technology services
SPOONER & SONSGAS & HEATING LTD
An engineering practice for software, web platforms and cloud infrastructure. The company designs, builds, integrates and maintains systems that organisations depend on daily.
- Discipline
- Software engineering
- Delivery
- Incremental
- Language
- English
- Contact
- annieevans198737@gmail.com
§ 02Technology focus
A narrow focus:
systems that must keep working
The company concentrates on the parts of technology that carry operational weight — the applications staff use every day, the interfaces customers see, the pipelines that move data, and the infrastructure underneath all of it.
That focus shapes the technical choices. Established languages, well-supported frameworks and explicit architecture are preferred over novelty. Every component is expected to be readable by another engineer, testable in isolation and replaceable without a rewrite of everything around it.
Work is scoped so that value arrives in stages. A first release is deliberately small and observable, and later stages build on what that release proves.
§ 03IT service areas
Where the work sits
02
Web platforms
Browser-based products, portals and content-driven sites built for maintainability and measurable performance.
03
Cloud and infrastructure
Environment design, deployment pipelines, observability and cost-aware resource configuration.
04
Integration
Connecting internal systems and third-party services so information moves reliably between them.
05
Automation
Replacing repetitive manual steps with scheduled, auditable processes that report their own outcomes.
06
Support and maintenance
Ongoing correction, dependency upkeep and incremental improvement after a system goes live.
§ 04Custom software development
Software written for one specific problem
Custom development is appropriate when off-the-shelf software forces an organisation to distort the way it works. The company builds applications around existing processes instead of the other way round.
Domain modelling
Processes, rules and vocabulary are written down before code is produced, so the software uses the same terms as the people who operate it.
Architecture
Boundaries between modules are defined early. Data ownership, failure behaviour and extension points are decided deliberately rather than emerging by accident.
Deliverables
Source code, migrations, automated tests, deployment configuration and written notes describing how the system is run.
§ 05Web applications and digital platforms
Platforms that hold up in a browser
Front-end work is treated as engineering, not decoration: state, accessibility and performance are part of the specification.
Interfaces
Component structures, layout systems and typographic scales that stay coherent as a product grows.
Accessibility
Semantic markup, keyboard reachability, contrast and reduced-motion behaviour considered during implementation.
Performance
Asset sizing, lazy loading below the fold, caching and rendering strategy chosen per page.
Content
Editorial structures and metadata so pages are readable by people and by crawlers.
§ 06Cloud and infrastructure
Infrastructure described in code
Environments are defined in configuration so they can be recreated, reviewed and changed with the same discipline as application code.
- Separate development, staging and production environments with parity where it matters.
- Automated build and deployment pipelines with the ability to roll back a release.
- Logging, metrics and alerting configured so problems are noticed before users report them.
- Backup and restore procedures written down and exercised, not assumed.
- Resource sizing reviewed against actual usage to keep running costs proportionate.
§ 07Systems integration and automation
Making separate systems behave as one
Most organisations run several tools that were never designed to work together. Integration work maps the data each system owns, agrees a single source of truth for every field, and builds the transfer layer between them with retries, validation and clear error reporting.
Automation follows the same principle. A manual routine is documented step by step, then implemented as a scheduled or event-driven process that records what it did and raises an alert when a step fails.
Typical artefacts
- 01Interface inventory listing each system, its data and its access method.
- 02Field-level mapping with transformation rules and validation constraints.
- 03Synchronisation or event flow with defined retry and failure handling.
- 04Runbook describing how to inspect, replay and correct a failed transfer.
§ 08Security-conscious engineering
Security treated as a habit
Security practices are built into ordinary engineering work rather than added at the end. The aim is to reduce avoidable exposure; no engineering practice can promise that a system will never be attacked.
Least privilege
Access granted narrowly, reviewed when roles change.
Input validation
Untrusted data validated at the boundary it enters.
Secret handling
Credentials kept out of source control and rotated.
Dependency hygiene
Third-party packages tracked and updated deliberately.
Transport security
Encrypted connections and sensible default headers.
Auditability
Meaningful logs that support investigation after an incident.
§ 09Project delivery process
How a project moves
Phase 01
Framing
The problem, current systems, constraints and the definition of a good outcome are written down and confirmed.
Phase 02
Scope and plan
Work is broken into deliverables with assumptions and open questions stated explicitly, so unknowns are visible rather than hidden in an estimate.
Phase 03
Build in increments
Short cycles produce working software. Each increment is reviewed against the framing document and the plan is adjusted.
Phase 04
Verification
Automated and manual checks are run against agreed acceptance criteria before anything reaches production.
Phase 05
Release
Deployment runs through a repeatable pipeline with a rollback path and post-release observation.
Phase 06
Iterate or hand over
Work continues into maintenance, or documentation and access are handed to the team that will own it.
§ 10Quality assurance and testing
Testing that describes intended behaviour
Tests exist to state what a system is supposed to do and to notice when that stops being true. They are written alongside the code they cover, not retrofitted at the end of a project.
Unit tests
Individual functions and modules checked against their contracts, including edge cases and error paths.
Integration tests
Behaviour across module and service boundaries, including database access and external interfaces.
End-to-end checks
Critical user journeys exercised through the interface in a browser.
Regression suite
Every reported defect gains a test so the same fault is caught if it returns.
Manual review
Exploratory checking of interfaces, content and accessibility before release.
Pipeline gates
The test suite runs automatically on every change; failures block the release.
§ 11Maintenance and ongoing support
The work after launch
A system in production changes even when nobody adds features: dependencies age, volumes grow and requirements shift. Maintenance keeps that drift under control.
Corrective
Investigation and repair of reported defects, with a written explanation of the cause and the change made.
Preventive
Dependency and platform updates, security patching, log and metric review, and removal of code that no longer serves a purpose.
Adaptive
Adjustments as external interfaces, regulations or usage patterns change around the system.
Evolutionary
Small, agreed improvements delivered on a regular cadence instead of accumulating into a costly rewrite.
§ 12Collaboration principles
How the company works with clients
Write it down
Decisions, assumptions and open questions are recorded in plain English so nobody relies on memory.
Show working software
Progress is demonstrated with something that runs, at short and predictable intervals.
Say what is uncertain
Where an estimate depends on an unknown, the unknown is named instead of padded over.
Leave systems understandable
Documentation, readable code and access handover so the client is never dependent on a single explanation.
Respect existing constraints
Budget, internal policy, legacy systems and staff capacity are treated as part of the design problem.
§ 13Frequently asked questions
Questions and answers
What kinds of projects does the company take on?
Work centres on custom software, web applications, cloud environments, integration between systems, automation of manual processes, and long-term maintenance of systems already in production.
How does an engagement usually begin?
It begins with a written description of the problem, the systems already in place, and the outcome expected. That description is turned into a scope note that lists assumptions, open questions and the first deliverable.
Can existing systems be improved rather than replaced?
Yes. Incremental work on an existing codebase or infrastructure is common: adding tests, isolating risky areas, updating dependencies and extracting components before any larger change is considered.
How is progress made visible?
Through working software at short intervals, written notes on what changed, and a shared record of open issues. Estimates are revised as understanding of the problem improves.
How is quality handled?
Automated tests are written alongside features, changes are reviewed before merging, and releases run through repeatable pipelines. Testing reduces defects; it is not presented as a guarantee of a defect-free system.
What happens after delivery?
Maintenance covers dependency updates, security patching, monitoring review, correction of reported defects and planned improvements agreed in advance.
How can an enquiry be sent?
By email to annieevans198737@gmail.com. Including the goal, current systems, constraints and timing helps produce a useful first response.
§ 14Contact information
Enquiries
Enquiries are handled by email. A short description of the goal, the systems already in use, any constraints and the intended timing is enough for a considered first reply.
Company
SPOONER & SONS GAS & HEATING LTD
annieevans198737@gmail.com
Shown as plain text. This website contains no clickable elements.