Backend
Production PHP systems with clear domain boundaries, predictable data flows and APIs built to be consumed for years.
- PHP
- Laravel
- Symfony
- REST APIs
- Domain-driven architecture
- MySQL
- MariaDB
- Redis
Capabilities
Four areas that usually have to work together in one system: a solid backend, a maintainable frontend, infrastructure that stays out of the way, and AI that is actually connected to something.
Production PHP systems with clear domain boundaries, predictable data flows and APIs built to be consumed for years.
Typed, maintainable interfaces on top of those systems — from admin dashboards to customer-facing apps.
Reproducible environments, automated pipelines and deployments that are boring on purpose.
AI wired into real business systems: agents with tools, retrieval over enterprise knowledge, structured workflows.
Toolchain
The technologies I use daily. Tools are chosen per project, not the other way around.
How I work
I take ownership of a project rather than picking up isolated tickets: architecture, implementation, integrations, deployment and the iterations after go-live.
01
Business context, constraints and the actual bottleneck — before any technology decision is made.
02
Domain boundaries, data model, integrations and the failure modes that matter.
03
Core domain, APIs and tests first, so later features do not fight the base.
04
External services, payment providers, enterprise systems, retrieval and agents with tool access.
05
Automated tests, error tracking, performance work and sane defaults under load.
06
Dockerised environments and CI/CD pipelines that make releases uneventful.
07
Measure, refactor and extend — with the architecture kept honest as scope grows.
Tell me about the system you need built, rescued or extended.