Review as a habit
Every change is read by someone other than its author before it reaches a shared branch.
About us
An IT company built around clear engineering and clear communication
SUN & HEAT SOLUTIONS LTD provides software development, cloud, data and IT consulting services. We work in writing, we explain our reasoning, and we build systems that other people can understand and maintain after we hand them over.
Mission
To make technology decisions legible. We build software and infrastructure that solve a stated problem, we describe the trade-offs behind each significant decision, and we leave the client in a stronger position to operate and change the result than they were before the work began.
Vision
A working environment in which organisations are not dependent on any single supplier to understand their own systems. We would rather be chosen again because the previous work held up than retained because nobody else can read the code.
Working principles
- 01
Write it down
Scope, assumptions, risks and decisions live in written form so they can be reviewed, challenged and revisited.
- 02
Say what is uncertain
Unknowns are named early. An estimate given without its assumptions is not useful to anyone.
- 03
Small, reviewable steps
Work arrives in increments that can be inspected, so course corrections are cheap.
- 04
Leave the system better documented
Handover material is written during the work, not assembled after it.
Engineering mindset
We treat software as something that will be read far more often than it is written. That shapes the everyday choices: explicit names over clever abstractions, boundaries that reflect the domain, tests that describe intended behaviour, and dependencies chosen for their support horizon rather than their novelty.
It also shapes what we refuse to do. We avoid speculative complexity built for requirements that have not been stated, and we avoid hidden coupling that makes a system cheap to extend once and expensive to change thereafter.
Approach to responsible technology
Systems collect data, make decisions and affect people who never agreed to be part of them. We take a conservative position: collect the minimum data required for the stated purpose, keep it only as long as it is needed, and make the retention rule explicit rather than incidental.
Data minimisation
Fields are justified by a purpose before they are stored.
Accessibility
Interfaces are built to be operable by keyboard and readable by assistive technology.
Efficiency
Lighter systems cost less to run and fail less often; performance is a design concern from the start.
Quality and security culture
Secrets stay out of code
Credentials live in managed secret storage, with rotation possible without a code change.
Dependencies are watched
Third-party libraries are kept current, and updates are applied deliberately rather than in a rush after an advisory.
Incidents produce changes
When something fails, the fix includes whatever prevents the same class of failure recurring.
Collaboration philosophy
Good technical work depends on an honest working relationship. We ask direct questions early, we prefer a difficult conversation about scope over a comfortable one that postpones the problem, and we expect the same in return. Clients keep control of priorities; we take responsibility for how the work is engineered and for telling you when a requested approach carries a cost worth reconsidering.
Contact information
Enquiries about our services, working models or an existing system are handled in writing by email.