Loading...
Who I Am
Systems should survive the first deployment and the thousandth. I design for operability and quiet confidence — knowing it will work when it matters.
I work across frontend architecture, backend services, AI integration, and developer tooling. The problems I choose live at the boundary of engineering, product strategy, and user experience.
I write code. I design systems. They work, they feel right, and they evolve.
Engineering Principles
Every feature is part of a larger architecture. I design for composability, resilience, and evolution — ensuring each component earns its place in the system.
Repetition is a signal. I invest in tooling, pipelines, and automation early — so the team focuses on problems that require human judgment, not mechanical effort.
Opinions are cheap. Data reveals truth. I build observability into everything I ship, so decisions are grounded in evidence of what actually happens.
Code that is easy to read and change outlasts code that is impressive but opaque. I optimise for the next engineer who touches this system.
Technology is a means, not an end. Every decision is measured against the business outcome it enables. Elegant code solving the wrong problem is still the wrong solution.
Currently Building
Projects in various stages — from design through production.
A CRM serving 12,000+ users with role-based access control, real-time collaboration, and AI-assisted pipeline management. Used daily by a growing sales organization.
Phase 3 of 4
Multi-tenant RBAC
Internal platform unifying deployment, monitoring, and collaboration tooling across engineering teams — reducing context switching and deployment friction.
User Acceptance
Onboarding flow completion
Event processing system designed for sub-100ms query latency across streaming event data. Built for internal product analytics use cases.
Architecture Review
Data model finalization
Engineering Dashboard