My name is Aleksey, I am a developer
Six years building websites and systems that people use every day.
What I have worked on
Logistics. I built the backend of a system that international freight passes through: from the order to the client invoice. The system is large, around two hundred thousand lines, and I worked across every part of it. For the same company I built the client area, the public websites and a shipping calculator that works from real tariffs right on the page. One product seen from every side — from the landing page to the database.
Banking. I worked on a lending platform: many services, complex processes, strict security requirements. I cannot go into detail — NDA.
Low-code. I designed a platform where an application is described by configuration rather than code: which screens, which data, who sees what. Launching a product for a new industry does not mean copying and rewriting code — it means writing configuration.
My own. I built a household budget service in Telegram. Entirely alone: designed it, wrote it, deployed it, and I keep it running. I also run my own cluster, where my projects live.
Education
Demidov Yaroslavl State University, computer security. In practice that means one thing: I think by default about how a system can be broken. Encryption, secrets, access control are part of the project from day one rather than something bolted on at the end.
At university I also did research — control of a group of unmanned aerial vehicles. It has nothing to do with websites, but the habit of taking a solution all the way rather than to “seems to work” comes from there.
How I think about the work
All my projects share one idea: a system should change without a programmer. A process is edited in configuration, not in code. A page is assembled by a manager from ready blocks. One codebase serves different products, and the differences live in settings. I build so that you do not have to call me for every edit.
What I take on
Websites — but the kind you can grow later rather than rebuild. Client areas, internal systems, automation. Integrations: connecting a CRM, accounting, payments, third-party APIs. Telegram apps and bots.
If I see that a site builder is enough for you, I will say so and suggest which one.
Why I am easy to work with
One project at a time. I do not take the next one until the first is delivered — so I go deep and I do not disappear.
Everything stays with you: the code, the access, the documentation. If you want to move to another developer, you can, without trouble.
I say things straight. If the task is cheaper solved without me, I will say so. If I am not sure about a deadline, I will not promise one.
I have built systems that run under load and handle real money. After that you approach any project with a different kind of care.
I write tests and documentation as the work goes, not “later”. Later usually does not arrive.
Stack
.NET and C# on the backend. React and TypeScript on the frontend, Astro and Next.js for websites. PostgreSQL, GraphQL. Docker, Kubernetes, CI/CD. WordPress — when it is genuinely the right tool.
If your project is written in something else, that is not a problem. Working through unfamiliar code and unfamiliar systems is routine for me: the hard part is usually understanding how a system is put together, not which language it is in.