—About us
A software company organised around maintainability
SASOLIDBUILD LTD designs, builds and maintains software for organisations that depend on it operationally. The work covers custom applications, web platforms, backend services, integrations and cloud infrastructure.
01Purpose
Software should stay useful after the first release
Our purpose is to produce systems that remain economical to change. The cost of software is rarely concentrated in its first version; it accumulates in every later modification, in every incident, and in the time it takes a new engineer to understand what exists.
That view shapes practical decisions: preferring explicit structure, documenting reasoning, keeping tests close to business rules, and treating deployment and operations as part of the product rather than as an afterthought.
02Working principles
Clarity before code
Requirements are written down and agreed before implementation. Where something is unknown, it is recorded as an open question instead of being filled in with an assumption.
Small, reversible steps
Changes are delivered in increments that can be reviewed, tested and rolled back. Large irreversible moves are broken down until they stop being irreversible.
Readable over clever
Code is written for the person who will read it next. Structure, naming and explicit behaviour are preferred to compact solutions that require explanation.
Tested where it matters
Business rules, boundaries and integrations are covered by automated tests. Coverage is directed at risk rather than at a percentage figure.
No hidden state
Configuration, deployment steps and operational procedures are documented and versioned, so nothing essential lives only in one person's memory.
Honest reporting
Progress, obstacles and estimates are communicated as they are. Problems are raised early, when there is still room to respond to them.
03Approach to engineering
Constraints first, architecture second
Design begins with constraints: the data that must be stored and for how long, the volume and shape of traffic, the systems that must be integrated, the regulatory conditions that apply, and the team that will operate the result.
Architecture follows from those constraints. We favour the simplest structure that satisfies them, and we keep boundaries narrow enough that a component can be replaced without rewriting its neighbours. Technology selection is documented with its trade-offs, including what it will cost to maintain.
Where an existing system is involved, we work with it as it is: measuring current behaviour, adding tests around it, and changing it in steps that keep it operational.
04Collaboration practices
Few meetings, complete records
Collaboration is organised so that the state of a project is legible without a meeting. A shared backlog holds the current scope, written updates describe what changed and why, and a running environment shows the software as it stands.
Regular sessions are used for decisions that genuinely need discussion: priorities, trade-offs and unresolved questions. Everything else is handled in writing, which keeps the project workable across time zones and preserves context for people who join later.
Clients keep ownership of their repositories, infrastructure accounts and data throughout the engagement.
05Commitment to maintainable software
Every engagement ends with a system another team could take over.
Handover material is produced during the project, not assembled at the end: architecture notes, data model documentation, environment and deployment instructions, operational runbooks and a record of significant decisions.
Dependencies are kept current, deprecated interfaces are replaced deliberately, and known technical debt is tracked in the open so it can be scheduled rather than discovered.
SASOLIDBUILD LTD · dariusjaeger357@gmail.com · sasolidbuild.com