Full-stack developer · Johannesburg, ZA
I’m an IT student who ships real software for paying clients. The most recent is a complete healthcare practice platform — booking engine, payments, authentication, two separate consoles and POPIA-conscious data handling — running in production today.
Featured case study
Be Whole Care was booking by phone and chasing payments by hand. I replaced the whole operation — clients now self-book and pay online, and the practitioner runs the business from an admin console. Sole developer: design, build and deploy.
The detail I’m proudest of
Most booking systems check availability in application code, which still loses a race between two people clicking at the same moment. Here the rule lives in the database as a constraint — so it holds under concurrent requests, and under any code path I might have forgotten.
Booking engine
Real-time slots calculated from working hours, existing bookings and blocked time, with Google Calendar sync so the practitioner’s own diary stays the source of truth.
Payments
Peach Payments / PayFast on hosted checkout, with server-side webhook verification — payment state is only ever trusted from a verified callback, never a browser redirect. No card details touch the app, which keeps PCI scope out of my stack.
Auth & security
Two consoles
Notifications
Email and WhatsApp for bookings, reminders and changes — with delivery logging, so a failure is visible and recoverable.
Compliance
Explicit consent tracking and audit logs on sensitive actions, medical-aid disclaimers placed where they’re legally meaningful, and clinical notes kept separate from operational data.
Content & marketing
A subscriber-gated devotionals system — content tiers, subscription state and gated routes — plus the full public marketing site, all on the same codebase.
Tech specs
Grouped by what I’ve actually shipped with, not what I’ve read about.
Selected work
Every one is live or on GitHub — open them and look inside.
Most K53 study material is a PDF nobody finishes. This wraps the same syllabus in retention mechanics: study rooms, guided learning paths, an XP system, daily streaks and full-length mock tests across Code 1, 2 and 3. Installable as a PWA.
Inspects SPF/DKIM/DMARC, sender mismatch, URL risk and typosquats across 24 brand checks using 13 scoring rules, then exports a PDF report. Runs entirely client-side — no email content ever leaves the browser.
Watches every client relationship, drafts and times follow-up messages itself, and pauses the moment someone replies. Command centre with pipeline, sequences and analytics.
Quote management for construction repair businesses: line items, calculations and branded PDF output via jsPDF.
Multithreaded console applications with SQLite persistence over JDBC, custom exception hierarchies and full OOP design — inheritance, polymorphism and encapsulation applied properly.
Background
2026 — now
Building and maintaining production systems for South African businesses — healthcare, trades and services. Five clients live.
Studying
Full-time IT studies alongside client work — software development, databases and systems.
Ongoing
Security tooling, AI automation and systems design, built in the open on GitHub.
What you’d get