Projects
Selected engineering case studies: the problem, constraints, decisions, failure modes, and implementation evidence behind systems I owned.
Featured Engineering Cases
SOPFlow
A framework-agnostic SOP toolkit split into reusable core, diagram, and React packages with explicit workflow invariants and deterministic projections.
TEDx Payment Service
A ticketing backend that keeps order, payment, and ticket state explicit while Xendit completes payment asynchronously.
Notespace
A self-hosted workspace where notes, canvas, planning, Today, activity tracking, search, and recovery share one Go + SQLite ownership boundary.
Additional Work
9 entries Farm Hub (Fish Farming Feasibility Analysis) User inputs survive independently of generation while analysis sections remain inspectable and replaceable. Backend engineer / generation integration owner · Structured AI output · Data modeling · Failure handling → StunBy Cloud API (Bangkit Capstone) Compute can be replaced independently while data ownership and infrastructure boundaries remain explicit. Cloud/backend engineer · Cloud architecture · Persistent state · Infrastructure as code → GoHealth (Health & Nutrition Tracking) Meal/activity history, daily targets, BMI/weight records, and notification intent share one backend-owned model. Backend engineer / API owner · Domain calculations · Notification state · Authentication → Tangkapin (Weapon Detection & CCTV Reporting) Detection can trigger evidence without making model availability or confidence the sole authority for assignment and completion. Backend engineer / ML integration owner · Service contracts · Incident workflow · Evidence boundaries → Meets (Mentoring Platform) The delivered frontend supported 300+ mentors and 500+ mentees across mentoring, transaction, revenue, payroll, filtering, reporting, and live-session workflows. Frontend software engineer · Role-specific workflows · Live mentoring · Operational dashboards → Fixolution App (Workshop & Parts Platform) Three actor workflows share one API without relying on frontend-only permissions or client-supplied transaction truth. Full-stack engineer / application owner · Authorization boundaries · Transaction state · Booking workflow → Pinjamin App (Campus Room Booking) Approval, payment, refund, and user-facing updates can evolve without collapsing into one overloaded status field. Full-stack engineer / booking workflow owner · Payment callbacks · Booking state · Realtime delivery → Tracer Survey (Alumni & Supervisor) Survey flow and faculty access share one source of truth while graph validation remains an explicit hardening boundary. Backend engineer / API architecture owner · Survey graph · RBAC · Export workflow → Surau Quran API Student, teacher, attendance, tuition, registration, and payroll workflows share one backend source of truth without unnecessary distributed services. Backend engineer / API owner · RBAC · Payment lifecycle · Operational workflows →