Earlier
Functions, OOP, and a monolith
- Functions and procedural code
- Controller
- Facade
- Service
- Database and integrations
Experience
PHP is my primary working language. Since 2007, I have used it to build and evolve e-commerce, internal systems, APIs, and integration services.
I have worked with PHP since 2007. I started with a competition website in PHP 5 and gradually moved from custom websites and applications without a framework to larger e-commerce and internal systems.
Today, I use PHP mainly for backend logic, APIs, integrations, data, and the long-term development of products. Experience with several eras of PHP helps me design new system parts and modernise existing ones with care.
Not familiar with a term? Read a concise explanation in the glossary.
Progress over time
PHP 5 · early days
Architecture
PHP 7 · 2016—2025
Nette · team development
PHP 8 · today
How my approach evolved
As projects evolved, so did my way of working. From scripts built mostly around functions and a single monolithic project, I gradually moved towards object-oriented design, clearer code boundaries, and modularly structured applications. Depending on the scale and needs of a project, this may be a modular monolith or a standalone backend API.
I choose this degree of separation according to project complexity; for simple parts, I prefer a more direct solution.
Earlier
Today
Public code examples
A modular pickup-point importer from XML and APIs: Doctrine, value-object validation, tests, PHPStan, and further quality checks.
A PHP 8.5 and Laravel application for safe task scheduling across servers: Redis locks, UI / Application / Domain / Infrastructure layers, PHPUnit, PHPStan, and Deptrac.
I use today
I can review the current state of your application, propose the next step, or take ownership of a specific part of the system.