Your business objectives. My digital solutions.

About Me

I don't choose "frontend" or "backend" — I choose the task. I'm comfortable with any part of development: building logic on a server, linking services via an API, automating a routine, or just fixing something that hasn't worked for years.

The main thing for me is that the solution is reliable and the code is readable. I'm not afraid to go deep, understand someone else's legacy, or design a system from scratch. Technology is a tool. And the goal is a working product.

How I work?

Step1. I understand

I don't start writing code until I understand the task completely. I ask questions, listen, and understand the context. Sometimes the right question is more important than the right answer.

Step2.Designing

I'm thinking about architecture, choosing the right tools, and assessing the risks. My code has been around for a long time — I've been building reliability since day one.

Step 3. I write and show

I code it in iterations. You don't see the result at the end, but as you work. You can touch, comment, and edit the course on the fly.

Step 4. I rent and support

The final is not just "uploaded to the server". I make sure everything is working, and I stay in touch if something goes wrong.

Technical Website Audit and IT Consulting

Most popular

Technical Website Audit and IT Consulting

€450,00

This service helps you understand what’s really going on with your website or web application. I conduct a full technical inspection: performance, security, code quality, SEO basics, and server settings. You get a clear, jargon-free report with identified issues and their severity. More importantly, I provide a step-by-step action plan — what to fix first, what can wait, and how to do it. No guesswork, no hidden problems, just clarity. Whether you're planning a redesign, preparing for growth, or just worried something isn't right — this audit gives you peace of mind and a roadmap forward.

Why me?

Architectural Thinking

I design solutions so they scale and don't require rewriting within six months.

Broad Stack

Backend (Python, Node.js, PHP), databases (SQL, NoSQL), API, integrations, automation.I'll learn new things if needed.

Transparency

The code is clean, comments are included, and documentation is available upon request.You don't depend on me as the sole repository of knowledge.

Reliability

I don't disappear, I don't miss deadlines, and I don't make up excuses.

FAQ

It doesn't matter whether I've done it a hundred times or it's my first time. What matters is whether the problem is solvable and whether we have time for me to dive in. If a technology is new but fits the task, I'll figure it out. Programming is primarily about how you think, not about knowing specific tools.

That's completely normal. I don't expect a perfect technical specification from the start. We begin with a conversation: you describe the task in your own words, I ask questions, and together we clarify the details. Requirements may evolve as we work — that's a natural part of the process.

I write code that is readable, maintainable, and extensible. Even if another developer takes over the project six months later, they won't have to guess what I meant. Comments, structure, logic — everything should be clear. I also test key scenarios to make sure the code doesn't break on first use.

I don't disappear. If something goes wrong, I'm available to help figure it out. If you need additional work or new features, we discuss the scope and continue collaborating. I don't push monthly retainers, but I also don't abandon projects once they're "done."

Transparently. We agree on the scope of work, I provide an estimate, and either break the project into stages with milestone payments or agree on a monthly or hourly rate. You're not paying for "a pig in a poke." If at any point the requirements change, we adjust the plan and budget accordingly. The main goal is to make sure you're happy with the result.

Technical blog

How Often Should You Audit Your Website? (And Why It Matters)

Introduction Imagine you bought a car and decided never to have it inspected. No oil changes, no brake checks, no attention to strange noises. How long would that car last?...

Website Speed — Why It's Not Just About "Loading Fast"

Introduction "My site loads fine," business owners often say. But what does "fine" mean? Five seconds? Ten? For you, it might be fine, but for a user — it's a...

"It Works on My Machine" — Why Code Quality Matters Even If the Site Runs

Introduction The most dangerous words in programming: "It works on my machine." Yes, the site opens, buttons click, orders go through. But what's inside? Can it be maintained? How long...