TavongaTavongaChitambiraChitambira

Full Stack Engineer

Who's behind the code

I'm a software engineer specializing in production Machine Learning systems and real-time web apps, from training and deploying models to shipping the interfaces, APIs, and infrastructure that serve them. I care about the architectural decisions that separate a system that holds up from one that collapses under load.

Right now I'm building SyncBoard, a real-time multiplayer incident management workspace. Think PagerDuty meets Notion: Socket.io clusters bridged via Redis Pub/Sub, Yjs CRDTs for conflict-free collaborative editing, and an optimistic UI that rolls back gracefully when the network disagrees. The architecture problem is interesting; solving it without over-engineering it is the actual challenge.

In parallel, I'm building up my ML foundations, from linear algebra and backpropagation through to fine-tuning and production LLM systems, with a focus on cloud MLOps. The plan is to bring that into SyncBoard: auto-classification of incidents, runbook RAG lookup, and on-call summarisation.

Projects

Solo Architect & Developer @ SyncBoard

July 2026 — Present

  • RS256 JWT auth with refresh-token rotation in Redis, no auth library.
  • Cross-tenant requests always return 404, never 403, so tenants can't probe each other.
  • Ownership transfers only through one dedicated, atomic route.
Read the case study →
  • Next.js
  • Socket.io
  • Yjs
  • Redis
  • PostgreSQL
  • BullMQ
  • Stripe
  • Kubernetes

Writing

Article · Sep 2026

Why cross-tenant requests should return 404, not 403

A short note on information leaks in multi-tenant APIs and how SyncBoard avoids them.

Personal blogYet to upload. Coming soon.

Skills