I learn by building.

It started at an internet café.

My path into software was not especially formal. I started learning in an internet café, following curiosity from one small experiment to another. I do not remember every early project, but the habit stayed: try something, understand how it works, break a few things, and build it better the next time.

I've been working this way since 2018. Over time, experiments turned into freelance work, private client systems, open-source projects, and independent products.

Useful without needless ceremony.

I like software that is understandable, maintainable, and useful without needing a dramatic architecture diagram. I care about the experience of the people using the product and the developers maintaining it.

Three rules I return to.

• Simplicity first.
  Use the smallest sensible solution that can do the job reliably.
• Developer experience matters.
  Clear structure, useful tooling, and predictable workflows make better software easier to maintain.
• No-nonsense systems.
  Technology should solve the problem instead of becoming the problem.

Freelance and own products.

I currently work as a freelancer while continuing to build and explore products of my own.

I'm open to interesting website projects, web systems, and suitable software engineering opportunities.

Tools assist; decisions stay intentional.

I use AI-assisted development for exploration, implementation, and review, while keeping architecture, validation, and final decisions intentional.