I learned systems through operations before I learned them through code.

I write code deliberately — typically 30–60% of my time even in leadership roles — because architecture improves when decisions stay connected to implementation, debugging, and developer experience.

I also own the mechanisms around the code: hiring, architecture review, technical-debt planning, code ownership, engineering standards, and the continuous improvement of Definition of Ready and Definition of Done.

My goal is not process for its own sake. It is a delivery system where requirements are clearer, onboarding is faster, releases are more stable, and teams can see the actual state of work.

I owned LastMileLogistic in Moscow and worked as an owner, business developer, and executive across logistics and trading companies. My scope included sales, IT systems, warehouse operations, finance, service delivery, and small cross-functional teams.

Projects included northern deliveries to Pevek for gold-mining operations, export and complex trade, and supplying services, spare parts, and assemblies for trucks and special equipment.

This experience is still present in my engineering work: bottlenecks propagate, queues hide failure, handoffs need explicit contracts, and a locally optimal decision can damage the entire system.