CAPABILITIES
I split the work of keeping software running into four areas. Under each one are the projects that prove it.
The real interface work is deciding how many faces a system has: a public site, a customer account, an operations panel and a field user can share code, but not the same screens. In a multilingual product, language is a URL design question, not a translation file.
Repeated requests, half-finished payments, two writes at the same moment: these are everyday cases, not exceptions. I put permission and validation rules in one shared layer instead of repeating them per endpoint.
Code changes, data stays. Where a rule lives is the architecture decision itself: if the clash check sits in the database, no new screen can bypass it. Leaving no room for rounding errors in money is part of the same discipline.
Delivery doesn't end with the deploy command. Content that breaks the schema or a missing setting stops the build before it ever goes live, and after launch I monitor every project I run from one panel.
The two Laravel projects in the portfolio are deliberately left out of these four areas: I no longer pick PHP for new work. They ran as an education provider's portal and website in 2024–2025. What I carried forward is not the technology but two habits: designing URLs for multiple languages and never losing a published address.
Tell me what you want to build; I'll tell you up front how long it takes and what the sensible first step is.