I build backend systems, APIs and data-driven applications, primarily with Laravel and Python. My focus is on maintainable software, reliable infrastructure and decisions that hold up under review.
Most of my work starts at the same place: understanding how data actually moves through a system before choosing how it should be stored, cached or queued. That usually decides more about how a service behaves in production than the framework does.
I prefer boring, explicit solutions over clever ones, and I would rather ship a smaller system that is understood than a larger one that only works when nothing goes wrong.
I try to leave a trail behind each project: what is covered by tests, what has been measured, and what is still missing. Where a limitation is known, it is written down in the repository rather than left for someone to discover later.
Currently, I work mostly on Laravel services and REST APIs, with Python around them for tooling and data collection.
Areas I work with:
- Data modeling and consistency
- Authentication and session boundaries
- Background jobs and asynchronous processing
- REST API design
- Backend refactoring and system reliability
Understand the data flow first. Choose the architecture second. Keep the implementation explicit.
I value readable code, measurable performance, documented trade-offs and systems that remain predictable when things go wrong.





