I work mostly in Laravel: admin panels, workflow automation, and integrations for fintech and government-tech platforms. I favor domain-driven design, predictable architecture over clever shortcuts, and static analysis that keeps large codebases honest as they grow.

Lately I have been pairing that with Filament for internal tooling, and experimenting with AI-assisted developer workflows and voice interfaces on the side.

Backend

Frontend

Data & Infrastructure

CertiCode Project Directory System Private repository · Laravel · Filament · MySQL A project and certification directory system with role-based access control, audit trails, and document workflow tracking.

NDDU Sanction System Private repository · Laravel · MySQL A case management system for tracking and processing disciplinary sanctions through structured review workflows.

TASYO AIMS Private repository · Laravel · Filament · MySQL An academic information management system covering records, enrollment, and role-based reporting dashboards.

Merky Private repository · Laravel · React · MySQL A product platform with a Laravel API backend and a React frontend.

• Predictability over cleverness. Code should be boring to read and easy to trace, even under pressure.
• Boundaries before features. Clear module and domain boundaries first, so features grow without turning into spaghetti.
• Security by default. Input validation, authorization checks, and audit trails belong in the design, not bolted on later.
• Pragmatic scaling. Build for the traffic and team size you actually have, not the one you might have someday.

Open to freelance Laravel and Filament work. LinkedIn DMs are open, and I read every one.