Software Engineer · Product & Backend Systems
Cape Town, South Africa
Portfolio · CV · LinkedIn · Email
I build operational products from interface to data model, with particular attention to retries, access boundaries, and recoverable failures. My public work spans Next.js and Go products, Rust tooling for bounded payment-failure testing, and maintainer-merged changes to Turso and CrossHair.
| Project | Engineering question | Inspect |
|---|---|---|
| ClinicPulse | How does a field report survive weak connectivity without becoming a duplicate or hiding a conflict? | Offline sync implementation · Regression tests · Demo |
| StrataHQ | How do bank-statement rows become reviewable payments when references are ambiguous? | Import service · Matching tests · Seeded beta demo |
| TxProof | What can an ambiguous provider outcome do to a payment flow, and how can the failure be replayed? | Campaign planner · Configured-run regression · CI |
ClinicPulse is an alpha demonstration. StrataHQ is a beta demonstration with seeded data. TxProof searches bounded histories against a synthetic reference application. The linked code and tests show the implemented boundaries.
- Turso, Rust: Contributed two schema-transition correctness fixes to a SQLite-compatible engine. The work covers preserving
AUTOINCREMENTstate afterDROP COLUMNand clearing stale sequence metadata after anALTER COLUMNtransition. PR #6993 · PR #7117 - CrossHair, Python/C: Moved callable-target normalization into the C tracer while preserving keyword handling, dispatch, and descriptor errors; added behavioral regression coverage. PR #413
- Java commerce and search backend: Java 21/Spring Boot API with SQL LIKE, PostgreSQL full-text, in-memory, and OpenSearch paths, Kafka indexing, asynchronous benchmark jobs, and authorization/endpoint contracts.
- Guard Rail: Beta Rust policy runtime for internal API traffic, credential stripping, audit records, and replay against recorded or current policies.
I also study algorithms in C++ and Java. Current confidential full-stack work includes C#; client and implementation details remain under NDA.
If a project is relevant to your team, I am happy to walk through the failure case, the tradeoffs, the test boundary, and what I would change for a production deployment.

