WS
Let's talk

Elsewhere

Decorative 3D visualisation; all content is available as text.

Tech Lead @ Data Age · Team Lead @ Rapidev Labs

I lead teams that ship production software — and I make the web move.

Hospital operations, learning platforms, creator-discovery tooling, procurement systems. Technical direction, code review and mentorship by day; real-time 3D on the web that holds frame rate on a mid-range phone. An AI agent fleet runs review, security and performance passes inside the delivery loop; decisions and standards stay with me.

See the workLet's talk
Years shipping
6+
Domains shipped
7
Specialism
WebGL / real-time 3D
Scroll
  • Healthcare
  • Education
  • Creator economy
  • Procurement / ERP
  • Social services
  • Developer tooling
  • Interactive 3D
  • AR / XR
Production platforms led/shipped
10
Domains shipped
7
Roles held today
2
Concurrent production systems monitored
6

01 — Selected work

Selected work

One habit, across every domain: decide the architecture early, make every migration reversible, and leave the next engineer a system they can read.

Interactive 3DClient codebase

gabar

Real-time 3D web experience: rigid-body physics, spatial audio, mobile joystick controls, tuned to hold frame rate on mid-range devices.

  • Three.js
  • React Three Fiber
  • drei
  • Rapier
  • Howler
Architecture walkthrough on request
HealthcareClient codebase

Vantage Health System

Hospital operations platform: containerised services, structured logging, QR-coded records, generated reporting decks.

  • Node
  • Express
  • Docker
  • Winston
  • PptxGenJS
Architecture walkthrough on request
Social servicesClient codebase

we-assist-you

Assistance platform on a typed backend with enforced security rules, conventional commits, staged builds; monitored in production.

  • TypeScript
  • Firestore
  • React
  • TanStack Query
  • Zod
  • Sentry
Architecture walkthrough on request
Creator economyClient codebase

heycreator

Creator-discovery platform with automated enrichment pipelines and reversible data migrations (dry-run, apply, rollback).

  • Next.js
  • TypeScript
  • Firebase
  • Apify
  • Puppeteer
  • Playwright
Architecture walkthrough on request
EducationClient codebase

learnx

LMS with rich-text authoring: drag-and-drop curriculum building, tables, code blocks, inline media.

  • React
  • Express
  • Firebase Admin
  • TipTap
  • dnd-kit
  • Zustand
Architecture walkthrough on request
Developer toolingPublic

PR-Pulse

Pull-request performance and review-signal tooling. Public.

  • TypeScript
  • Next.js
  • Vercel Blob
  • Motion
Read
AR / XRIn preparation

[AR project name]

Augmented reality product visualisation letting customers place true-to-scale models in their own space before buying.

02 — How I Lead

Accountable for how it's built, not just that it shipped.

Four pillars that follow me into every codebase.

Pillar 01

Technical direction

  • Architecture standards decided early and written down, not discovered in review.
  • Migrations reversible by design — dry-run, apply, rollback — so no release is a one-way door.
  • Honest error handling: failures surface with context instead of being swallowed.

Pillar 02

Code review & standards

  • Typed backends — the contract lives in the code, not in a document nobody opens.
  • Security rules enforced at the boundary rather than assumed by the caller.
  • Conventional commits and staged builds, so history and releases both stay readable.

Pillar 03

Mentorship & delivery

  • Engineers grow through review — it is the default unit of work, not a gate at the end.
  • Accountable for how it's built, not just that it ships.
  • Handover documentation written while the context is still fresh.

Pillar 04

AI-native delivery

  • An agent fleet sits inside the delivery loop: a lead agent dispatches specialists for code review, security and performance passes, and drafts the first cut of specs and handover notes.
  • Every agent pass is evidence for a human review, not a replacement for one — findings arrive with file and line, and the suite has to be green before anything is read.
  • Decisions and standards stay with me: no agent ships or changes a rule.

How I run a project

  1. 01
    Discovery

    Constraints, users, and the one thing that must not break.

  2. 02
    Architecture

    Data model, boundaries, migration strategy. Written before code.

  3. 03
    Delivery cadence

    Staged builds, weekly demo, review as the default unit of work.

  4. 04
    Launch

    Rollback rehearsed, logging in place, on-call agreed.

  5. 05
    Operate

    Monitored, measured, and handed over so it outlives me.

03 — Craft: 3D & AR

The thing that surprises people: WebGL that runs at 60 fps on a mid-range phone.

Rigid-body physics, spatial audio, mobile joystick controls — and the performance budgets that make it viable.

The physics engine ships in a later milestone — Enable physics and Reset are inert until then, and change nothing but this button’s own label.

04 — Stack

What I reach for

Languages

  • TypeScript
  • JavaScript
  • SQL
  • Python
  • GLSL

Frontend

  • React
  • Next.js
  • Tailwind CSS
  • TanStack Query
  • Zustand
  • TipTap
  • dnd-kit

Backend & Data

  • Node.js
  • Express
  • Firebase
  • PostgreSQL
  • Zod
  • Supabase
  • NestJS
  • Apify

Cloud & DevOps

  • Vercel
  • Docker
  • GitHub Actions
  • Google Cloud
  • Sentry

3D & Creative

  • Three.js
  • React Three Fiber
  • WebGL
  • drei
  • Rapier
  • Howler
  • WebXR
  • Blender

Tooling & Practice

  • Git
  • ESLint
  • Conventional commits
  • Playwright
  • Vitest
  • Puppeteer
  • Linear
CoreWorkingFamiliar

05 — Experience

Experience

  1. Rapidev Labs

    Harare, Zimbabwe

    1. 2026 — present

      Team Lead

      • Lead the engineering team while still shipping as a senior engineer: planning, review and production releases.
      • Run an AI agent fleet inside the delivery loop — a lead agent plus specialists for code review, security and performance passes.
      • Decisions and standards stay with me; the agents draft and check, they do not sign off.
    2. 2024 — 2026

      Senior Software Engineer

      • Design and ship full-stack features end to end — data modelling through deployment.
      • Own API design, typed backends and the pipelines behind production releases.
      • Make migrations reversible: dry-run, apply, rollback, with honest error handling.

  2. Data Age

    Harare, Zimbabwe

    1. 2026 — present

      Tech Lead

      • Set technical direction and architecture standards across the engineering team.
      • Run code review as the main channel for standards and mentorship, not a defect net.
      • Accountable for how the work gets built, not only that it shipped.
    2. 2025 — 2026

      Senior Software Engineer

      • Built and shipped full-stack features end to end — data modelling through deployment.
      • Typed APIs and backends, with the contract living in the code.
      • Reversible migrations: dry-run, apply, rollback.

  3. Earlier engineering roles

    1. 2020 — 2023

      Software Engineer

      • Built and maintained production web platforms across healthcare, education and procurement.
      • Moved from feature work to owning architecture and release process.

06 — Writing & elsewhere

Writing & elsewhere

Feed not wired up yet

Live posts land here once the Medium feed is connected. Nothing else on the page depends on it.

Read on Medium →
LinkedInGitHubXMediumInstagramReddit

07 — Contact

Open to consulting & collaboration.

Leading a build, untangling an architecture, or making something run at 60 fps — if it's an interesting problem, I'd like to hear about it.

LinkedInlinkedin.com/in/wieslaw-samushonga-3b3913154GitHubgithub.com/JxstWieslaw

No newsletter, no tracking pixel.