About me
I've been programming for years, and the reason never changed: I enjoy understanding how things work. At first it was code for code's sake — making the machine obey. Over time, the interest moved up: the product, the business rules, the real problem behind the request. Today, the part of a system that interests me most is the one explaining why it exists the way it does.
narrative
I work as a full stack engineer with legacy and modern systems. Legacy taught me respect for real constraints — nothing gets rewritten from scratch for free; modern taught me to build structure that holds up to change. Both taught me the same lesson: understand before touching.
AI joining the development flow changed my tools, not my motivation. Manual programming became supervised planning: I define what must be true, delegate bounded execution, review against evidence. What used to be typing became process engineering — and I still enjoy the understanding part.
I keep custom tooling and automation routines because unrecorded repetitive work is work lost twice. And I study continuously — right now, AI-powered products, which I want to understand with the same depth I learned traditional systems. It's a study direction, stated as such.
skills
Full Stack Engineering
APIs, interfaces, databases, deploys.
Legacy and modern systems
Evolution and maintenance without heroic rewrites.
AI-assisted engineering
Planning, supervised delegation, review, verification gates — process described in How I work.
Automation and custom tooling
Repeatable checks and preserved context.
studying
AI-powered products
Study direction stated as such — not a credential.