{" "}
This page is not a traditional CV.
I work with real web projects — not abstract roles.
My experience is built around long-term support, system thinking,
and responsibility for decisions that affect real businesses.
Here you will not find buzzwords or exaggerated titles.
Instead, this is a structured overview of how I work,
what I focus on, and what kind of projects I take responsibility for.
<experience>
Experience built around real systems, evolving projects, and responsibility for decisions over time.
{ 2018
present }
{ 2018 present }
< >
// web architecture & long-term projects
Over the years, I have worked on business websites, medical platforms, and e-commerce projects with real operational requirements.
My experience includes:
- WordPress-based systems with custom structure
- OpenCart stores with complex catalog logic
- multilingual websites with technical SEO architecture
- long-term maintenance and system stabilization
Most projects evolve over time, not as one-time builds. Because of this, I focus on decisions that remain valid months or years later — not on temporary solutions.
{ core
focus }
{ core focus }
< >
// architecture & predictability
I take responsibility only for clearly defined scope and technically sound decisions.
This includes:
- structure planning
- platform choice
- data logic
- performance strategy
- multilingual architecture
Clear responsibility boundaries protect both sides and make long-term collaboration possible.
<skills>
These are not tools I collect, but areas I take responsibility for.
{/}
_structure & layout
Clean semantic markup, predictable layout systems, and maintainable structure.
I avoid visual complexity that breaks responsiveness or creates future maintenance problems.
{!}
_behavior & interaction
JavaScript is used when it solves real interaction problems, not for decorative effects.
Priority is given to stability, performance, and predictable behavior across devices.
{#}
_backend logic
Server-side logic focused on clarity and safety.
I avoid overengineering and poorly documented solutions.
Code must be understandable not only today,
but months later during maintenance.
{%}
_when justified
I work with React when the project truly requires it.
Framework choice is always dictated by project needs, not trends or personal preferences.
{*}
<contact_me>
... If you are looking for a developer who values clarity, structure, and long-term stability — we will likely speak the same language.
You can use the contact page to discuss your project or clarify technical requirements.