Technical expertise
I design and build backend systems, APIs, and full-stack products. The tools I use most often are Laravel, Django, Node.js, Express.js, React, Next.js, MySQL, PostgreSQL, and MongoDB, with Docker and VPS deployment when the project needs them.
Architecture
I start from the problem, the data, and the people who will operate the system. Tenant boundaries, authentication, and deployment are part of the design.
Development practice
- Server-side validation and authorization
- A structure another developer can follow
- Tests around publishing, access, and forms
- Docker, Linux, and CI/CD where they earn their place
Automation engineering
I build automation projects that remove repetitive manual work: order and inquiry notifications, scheduled reports, imports from spreadsheets, webhook bridges between apps, and queue workers that retry safely when a third party is slow.
Typical stacks are Laravel queues and scheduled tasks, Node or Python scripts for one-off integrations, and HTTP APIs when two systems need to stay in sync. The goal is always the same — a human should not copy the same data twice if software can do it once, reliably.
Published examples live under Projects (Automation category) with case studies that describe the problem and design without exposing private credentials or client secrets.
Management & ERP systems
I design and build management systems for organizations that have outgrown spreadsheets: hospitals and diagnostics, schools, resorts and restaurants, POS, inventory, and modular ERP platforms that tie finance, stock, and operations together. Each implementation is scoped to the client’s workflow — roles, approvals, reports, and audit trails — not a generic demo with fake numbers.
See the Management Systems category under Projects for the full list.
What this page will not do
It will not list unverified metrics. Impact is the problem, the design, and the result I can stand behind.