System Initialization
The Architect
& The Artifact
Are The Same.
The website itself is the proof of the programmer’s thinking. Interaction, layout, and motion communicate philosophy: precision, systems thinking, and deliberate design decisions.
01. Work
Case StructuresSys.001
AI-Driven Tech Architecture
Technology partner for Mole and Reka Studios, architecting event organizing products, real estate dashboards, and virtual try-on platforms.
Sys.002
Print Industry Quotation Engine
SaaS quotation platform built from scratch for the printing industry at TapPrint Sdn Bhd.
Sys.003
DOSM Data Migration System
Large-scale data migration for the Department of Statistics Malaysia at Fotia Solutions.
Sys.004
Multi-Tenant SaaS Delivery
Led a cross-functional team of 10 to develop multiple SaaS applications including eCommerce and telemedicine at Double Edge Technologies.
02. Systems
Thinking & ArchitectureDesign Principles
- 01Systems must be observable. If you cannot see its state, you cannot trust its behavior.
- 02Complexity is a liability. Isolate it, document it, or eliminate it.
- 03Data structures define the architecture. Algorithms are just the plumbing.
"AI is a structural material, not just a tool. Vibe engineering matters when architecting solutions."
— Margin note, Pragmatic Innovations, 2024
Event-Driven Microservices
SKETCH.01Decoupling state mutation from side effects using an append-only log.
State Machine Routing
SKETCH.02Deterministic UI transitions governed by explicit finite state machines.
03. Notes
Intellectual FragmentsThe Evolution of Tooling
Over 14 years, the stack shifts from Grails and Android Java to Spring Boot, React, and AI-assisted coding (Codex, Cline). The underlying architectural principles—cohesion, decoupling, and resilience—remain identical.
Data Integrity at Scale
When migrating 10 million census records, zero data loss isn't a goal; it's the baseline constraint. Algorithms must be designed defensively, assuming data corruption exists at the source.
Concurrent SaaS Delivery
Managing a cross-functional team of 10 to deliver 5 major platforms requires strict standardization. Shared libraries, consistent CI/CD pipelines, and unified deployment strategies are load-bearing structures.