Writing
Notes from building and operating systems.
Backend architecture, technical debt, engineering leadership, AI-native delivery, product work, and lessons from logistics. The archive contains older Russian and English technical notes; new long-form writing will be primarily in English.
Selected essays
Engineering practice.
Three operating essays connect architecture, AI-native delivery, and lessons from logistics with concrete decision tools.
Technical Debt as a Portfolio
A practical operating model for explicit risks, owners, treatments, and recurring investment.
AI-Native SDLC Without Losing Accountability
Bounded agent roles, delivery contracts, evidence, exceptions, and human release authority.
What Logistics Taught Me About Distributed Systems
Queues, handoffs, retries, buffers, observability, and recovery across physical and software systems.
Examples of technical debt
How technical debt appears in existing code and systems.
What is technical debt?
Definitions, prevention, and the practices used to keep debt visible.
Python app with Poetry and Docker
A compact reference for building a multi-stage Python image.
MySQL server has gone away
Understanding timeout-related connection failures.
Practical resources
Use the operating models.
Technical Debt Portfolio Register — a decision record, exposure assessment, and monthly/quarterly review checklist.
AI-Native Delivery Contract — a reusable acceptance packet with NFRs, evidence, rollout, rollback, and a human-agent decision map.
One Causal Pattern — a side-by-side remote-supply and multi-service failure case.
The complete historical archive is preserved, including older how-to posts and data-science notebooks. Some instructions may be outdated; publication dates remain visible for context.