Backend & distributed systems
Application cores, APIs, data flows and services that must coordinate reliably across boundaries.
Software Engineer · South Africa
About Victor Harding
Complex systems.
Clear thinking.
I’m Victor Harding, a software engineer based in South Africa. I build and think about software that has to remain dependable as its scale and complexity increase.
My work sits where software architecture meets operational reality.
My background is in backend engineering, databases, event-driven systems and platform architecture, particularly in complex financial and transactional environments.
These environments sharpened my interest in correctness, clear ownership and failure modes. A technical decision is rarely isolated: it shapes how safely a team can change the system, how clearly operators can understand it and how confidently the business can rely on it.
I care about making those trade-offs visible and building systems that remain understandable long after the first implementation.
What I work on
Foundations for software that needs to last.
Architecture & modernisation
Clearer system boundaries and practical paths for evolving critical software without unnecessary disruption.
Reliability & operations
Failure-aware design, observability and recovery paths that help teams operate software with confidence.
I’m most interested in systems where the details carry real consequences.
That includes software that coordinates financial or transactional work, protects data integrity, connects independently changing services, and supports teams as products mature.
I approach system design from both directions: the invariants the software must protect and the people who will need to build, operate and change it.
Correctness before cleverness. Complexity must earn its place.
Technical interests
01Distributed systems
02Backend engineering
03System design
04Databases & data integrity
05Event-driven systems
06Observability & reliability
Current areas of interest
Writing clearly about the architecture behind reliable software.
I’m currently exploring distributed coordination, system boundaries, transactional correctness, modernisation and the engineering practices that keep complex platforms legible.