About the way
I work

Who I Am as an Engineer

I prefer responsibility over narrow tasks

I am most useful in projects where the problem is not fully standard: existing systems that need to be understood, integrations that do not fit neatly into ready-made modules, or business logic that has to be designed before it can be implemented.

I do not usually work as a small isolated part of a large development machine. I am more effective when I can understand the technical problem as a whole and take responsibility for a meaningful part of the system.

Why I Build Software

I prefer systems that keep evolving

Building a feature is useful. Building a system that remains understandable, maintainable and adaptable for years is more interesting.

I am drawn to projects where software is not just a one-time delivery, but part of a long-running business process.

Why Complex Systems

The interesting part is usually behind the interface

Many web projects look simple from the outside. The real work often happens in the backend: data structures, imports, synchronization, content workflows, business rules, recovery logic and operational reliability.

That is the part of the work I usually find most valuable. A website is not only what visitors see. It is also the system that allows people to manage, update and operate it without breaking the business process behind it.

Technical Approach

Understanding the system before choosing the tools

I primarily build custom PHP applications and integrations with MySQL, JavaScript, APIs and server-side automation.

I do not usually rely on large frameworks for my own systems. For the type of work I do, I prefer understanding every layer of the application and keeping the implementation close to the actual business logic.

This is not a rejection of frameworks in general. It is a deliberate choice for projects where custom logic, maintainability and direct control over the system are more important than adopting a particular framework structure.

Why Agencies

I fit well where an agency needs additional technical depth

Small web studios and digital agencies often have strong design, client communication and frontend delivery processes, but occasionally receive projects with a more demanding technical core.

I enjoy becoming the technical partner who takes ownership of backend engineering while fitting into the agency's existing workflow.

Communication

Clear written work suits me best

I prefer written communication for requirements, decisions and progress updates. It keeps technical work precise, reduces misunderstandings and creates a useful record of decisions.

Calls are welcome when needed, but my preferred workflow is asynchronous: tasks, Git, documentation and structured written feedback.

Good Fit

Where I usually add the most value

I enjoy joining commercial projects where the technical work extends beyond standard website development: backend logic, API integrations, supplier synchronization, automation, existing PHP systems and long-term platform development.

I am comfortable working with both custom-built applications and established platforms such as WordPress, PrestaShop or other PHP-based systems. The technology stack itself is rarely a limitation.

The projects where I contribute the most are those that require understanding an existing system, designing custom business logic and building reliable solutions that can be maintained over time.