What matters here
I prefer a format where engineering looks less like a noisy banner and more like a composed system: there is a service, there is a problem, and there is a readable way to show what was built and how it works inside.
Personal website
A calm showcase of projects, technical notes, and engineering decisions.
This is where I collect products that can be opened, tested, and examined layer by layer: from document automation to public notes explaining how the systems are built and why they were designed this way.
Approach
One page, one route, one clear picture of the work.
The homepage is structured as a quiet landing page: first the overall feel of the work, then a concrete project, then public breakdowns, and finally a clean entry point into contact or code.
How the work is structured
01
Product and architecture are shown together so the result still exposes the system-level solution behind it.
02
Public articles extend the code and demo instead of repeating them as a formality.
03
Each section should lead into the next without overload, so the site reads like one coherent story.
Featured project
One service already surrounded by a demo, code, and public context.
Instead of an abstract portfolio block, the page highlights a project that can be inspected both as a product and as a system: from the initial idea to concrete engineering decisions.
Diploma Supplement Automation Service
A service for validating Excel grade sheets, highlighting problematic data, and assembling XML files for diploma supplements.
Automated validation and highlighting of problematic cells in Excel.
XML generation in the target “CyberDiploma 3.5.1” format.
Polyglot architecture with separate API, data-processing, and XML-generation layers.
Blog
Publications as an extension of project work.
These notes cover architecture, algorithms, and public updates for current initiatives.
ICT: from slant TEC to ionosphere maps — the IonMaps method
How the IonMaps module in ICT turns TEC-suite parquet output into regional maps of vertical total electron content: VTEC restoration from slant TEC, interpolation (linear, krigi...
Tea Taste: eight hidden backend failures a code review turned up
A walk through eight stability defects in the Tea Taste API found in a code review after the July release: a double HTTP server, errors that silently fell through past their han...
Tea Taste: VK login, a public feed, and an admin panel — a major update
A breakdown of a major Tea Taste (teaform.ru) update: VK ID sign-in, editable tastings, password recovery, a public feed with author profiles, in-app user feedback, and an admin...
Contact
If the goal is a clear engineering result, the fastest way to start is to look at the code, the demo, and the written breakdowns together.
GitHub remains the main entry point into the repositories and the demos around them, while the site works as a curated front layer: calm, clean, and open to technical discussion.