About me

My journey

Over the years, I’ve worked on a wide range of software projects — from internal tools to complex, long-running systems used daily by real users.

Early in my career, I focused primarily on writing code and delivering features. With time, I learned that the real challenges often appear months or years later — when systems grow, teams change and original assumptions no longer hold.

This experience shaped how I approach software today. I care deeply about clarity, structure and decisions that make future development easier rather than harder.

How I think about software

I believe software is a long-term investment. Every shortcut taken today has a cost that will eventually be paid by someone — often a future developer or the business itself.

I aim to reduce cognitive load wherever possible. Clear naming, explicit boundaries and simple flows help teams move faster in the long run.

I prefer boring, proven solutions applied thoughtfully. Novelty can be useful, but only when it clearly solves a real problem.

Architecture & responsibility

Good architecture is not about complexity or fancy diagrams. It’s about responsibility, ownership and understanding where changes should and should not happen.

I strive to design systems that are understandable even to someone who joins the project years later. Architecture should guide developers, not confuse them.

Working with people

I’ve worked both as an individual contributor and in leadership roles. I value communication, trust and shared ownership.

The best solutions often come from collaboration between developers, product owners and stakeholders. Technical decisions should serve the product, not ego.

What I deliberately avoid

Experience taught me that knowing what not to do is just as important as knowing what to build.

• • Over-engineering without clear value
• • Blindly following trends and hype
• • Architectures only one person understands
• • Decisions driven by ego instead of product needs

Beyond code

Outside of work, I enjoy music, sci-fi, fantasy and anime. Side projects allow me to experiment, learn and explore ideas without pressure.

Building my own micro-SaaS products helps me stay grounded in real-world constraints — from deployment to maintenance and user feedback.