Jan Mikoláš
Gradually
Components I learned in practice
- PrestaShop
- Symfony Console
- Doctrine
- Profiler and other libraries
Back to skills
Experience
Symfony experience
Symfony is my primary PHP framework. I use it to build current backends, APIs, and integration services that can evolve safely over the long term.
I found Symfony gradually, through its ecosystem.
My first significant Symfony experience came through PrestaShop. That is where I became accustomed to working with Symfony Console, Doctrine, the Profiler, and other libraries the ecosystem offers.
I then began using these tools in my own projects as well. When I built an API platform, there was no reason to look for different foundations — I built it directly on Symfony.
Not familiar with a term? Read a concise explanation in the glossary.
Progress over time
From familiar components to my primary framework.
-
PrestaShop
Hands-on experience with the Symfony ecosystem
In PrestaShop, I regularly worked with Symfony Console, Doctrine, the Profiler, and other libraries. It was not just framework theory, but daily work with tools while developing and maintaining e-commerce solutions. -
Independent projects
Gradually using Symfony libraries
I started transferring my knowledge of individual components into my own projects. Console commands, Doctrine, and debugging tools became a natural part of my work outside PrestaShop as well. -
API platform
The decision to build directly on Symfony
When building an API platform, Symfony made clear sense as a whole: a mature ecosystem, proven tools, consistent conventions, and a solid base for future development. -
Today
Symfony for current backends
Today, Symfony is my primary PHP framework for APIs, integration services, and applications where stable architecture, testing, and long-term development matter.
How my approach evolved
From individual libraries to a cohesive framework.
Symfony did not begin for me with one big switch. I first learned its specific tools in PrestaShop and gradually used them in my own code. Today, I use the whole framework where its conventions and ecosystem bring long-term value.
I do not introduce complexity just for the framework; I use its parts to the extent that matches the size and needs of the application.
Today
Symfony as a backend foundation
- HTTP APIs and Console
- Application and domain logic
- Doctrine and the data layer
- Integrations, queues, and infrastructure
Older public code example
Symfony importer — older project
I use today
Symfony stack for current backends
- Symfony 8.1
- Symfony Console
- Doctrine
- Profiler
- REST API
- OpenAPI / Swagger
- PostgreSQL
- Redis
- RabbitMQ
- PHPUnit
- PHPStan Max
Looking for a Symfony backend for your project?
I can design a new part of an application, help with APIs and integrations, or take on the long-term development of an existing solution.