- Four levels of testing
- Unit, integration, functional and end-to-end, on every project. They run automatically on every change, against a real database rather than stubs that agree with whatever you assumed. That way, even when big changes go in, code does not reach production unless it is safe.
- Built against anonymised data
- I never develop or test against real data. I work from an anonymised copy of your database that keeps the shape and the volume of the real thing, with nothing in it that identifies a person. The anonymisation routine scrubs the backups too, so data cannot survive in an old restore point.
- Role-based access control
- Each role sees only what it is entitled to, and the rules are enforced everywhere. An administrator controls exactly what each kind of user may do, and can revoke access instantly when the need arises.
- Backups every minute
- Every minute for the last hour, hourly for the last day, daily for the last month, monthly for the last year, and yearly after that. Restores can be run on demand, and an agent verifies the integrity of the data every night.
- Closed to the public internet
- Only the load balancer has a public address. The application cluster and the database cluster hold private addresses only, with public traffic to them blocked outright. Administration happens over VPN, to keep the data safe.
- Since 2014, across four sectors
- Medical, entertainment, beauty and tech. Very different domains with the same underlying demands: correct data, controlled access, and a system that does not give out exactly when you need it most. I can build in any domain: creativity has no limits, and experience brings seniority and expertise.